| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
sometimes Slack notification footer becomes just " at ".
It seems like `github.event.head_commit` is missing. Let me debug the
context.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Specify just a string
set @built_at as nil before testing
https://github.com/bundler/bundler/commit/578ec96c9c
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/a38161c5be
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/faccc522d1
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/23007cb107
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/52b6b94068
|
| |
|
|
|
|
|
| |
Our current set of specs is the same for all supported rubies, and we
should keep it that way.
https://github.com/bundler/bundler/commit/c9dc0f6f2c
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/8c7942d2c6
|
| |
|
|
| |
https://github.com/bundler/bundler/commit/36fb3287f4
|
| | |
|
| |
|
|
|
|
| |
rp() macro for debug also shows file location and function name
such as:
[OBJ_INFO:rb_call_inits@inits.c:73] 0x000056147741b248 ...
|
| |
|
|
|
| |
It seems that we cannot easily apply job-level [ci skip].
Therefore this commit skips only Tests step if it's [ci skip].
|
| |
|
|
|
| |
Some CIs report to two channels, and some others report to only one.
This makes it consistent. Only alert channel should be alerted.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It is defined since ruby 1.9.2.
https://github.com/rubygems/rubygems/commit/84981ca908
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
|
| |
|
|
|
| |
A "do" what has followed a token what has EXPR_CMDARG is for a block,
and in other cases "do" is for "while", "until" or "for".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without doing this, enabling a TracePoint on a method could lead to use
of moved objects. This was found by running
`env RUBY_ISEQ_DUMP_DEBUG=to_binary make test-all`, which sets
orignal_iseq then runs the compaction tests and the tracepoint tests.
Please excuse the lack of tests. I was not able to figure out how to
reliably trigger a move on a specific iseq imemo to make a good
regression test.
To manually confirm the problem and this fix, you can run:
```
env RUBY_ISEQ_DUMP_DEBUG=to_binary make test-all \
TESTOPTS="test/ruby/test_gc_compact.rb \
test/gdbm/test_gdbm.rb \
test/ruby/test_settracefunc.rb"
```
Or the following script:
```ruby
tp = TracePoint.new(:line) {}
1.times do # put it in a block to not keep these objects alive
objects = 10_000.times.map { Object.new }
objects.hash
end
1.times do
# this allocation pattern can realistically happen in an app
# at load time
beek = 10_000.times.map do
eval(<<-RUBY)
def foo
a + b
1.times {
4 + 234234
}
nil + 234
end
RUBY
Object.new
Object.new
end
beek.hash
end
tp.enable(target: self.:foo) { 234 } # allocate original iseq
GC.verify_compaction_references(toward: :empty)
GC.compact
tp.enable(target: self.:foo) { 234234 } # crash
```
[Bug #16098]
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Should compare minimum required version, and with the particular
macro defined for each version. Also made the error messages
consistent.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The second argument of ioctl seems to be int in Android.
Android is not a supported platform, but this one-line change allows
ruby to build by Android NDK r20.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Drop duplicated sample code
* Drop another style sample
https://github.com/ruby/ruby/pull/2389#issuecomment-522489520
* Update sample list
|
| |
|
|
|
| |
* It can invoke test-unit with envutil.rb
* refute_match of test-unit couldn't handle String instance.
|
| |
|
|
|
| |
```
sample/observ.rb:30: warning: assigned but unused variable - clock
```
|
| |
|
|
|
|
|
| |
because it has often hanged like
https://travis-ci.org/ruby/ruby/jobs/573691637,
and we also have almost the same test suite on GitHub Actions now, which
seems to be stable in `make check` so far.
|
| |
|
|
|
| |
Kernel#inspect does not call #to_s now
To follow https://github.com/ruby/ruby/commit/fd7dc23d281f38a71fa7f9c32812cd468c4b1788
|
| | |
|
| |
|
|
|
|
| |
displaying vm info as Linux and FreeBSD.
checking libproc as it is present only from 10.5 version.
https://github.com/ruby/ruby/pull/2384
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
* include/ruby/ruby.h: cast via `unsigned int` explicitly, to get
rid of signed extension by implicit integer promotion.
|
| | |
|
| |
|
|
| |
to suppress a waring for "unused variable"
|
| |
|
|
| |
as it failed randomly https://github.com/ruby/ruby/runs/196712109
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
MRI (#2113) [ci skip]
* Make it clear as possible that RubyVM is MRI-specific and only exists on MRI
* See [Bug #15743].
* Use "CRuby VM" instead of "Ruby VM" for clarity.
* Use YARV rather than "CRuby VM" for documenting RubyVM::InstructionSequence
* Avoid introducing a new "CRuby VM" term in documentation
|
| | |
|
