| Age | Commit message (Collapse) | Author |
|---|
|
Update included file list automatically.
|
|
|
|
|
|
|
|
|
|
The VPATH rule of NMake is different from others. Abandon using
them in the rules for the generated source, locate them in the top
source directory, as well as the generated library files of prism.
|
|
I spent a long time bisecting some largish program before realizing
that failure was in fact coming from the child timing out due to
zjit_bisect.rb not clearing the stdout and stderr pipe.
Fix the pipe deadlock by redirecting to /dev/null. This sacrifices
the debug output during boot, but for that we also get to remove
a lot of code and the dependency on Open3.
|
|
For most tests (except two), we don't need to change Encoding.default_internal
in assert_raise_with_message. We're trying to run the test suite across
multiple Ractors and modifying Encoding.default_internal can cause other
concurrently running tests to fail.
|
|
* Use unreleased version of rbs
* Skip all failing tests on windows
|
|
|
|
Also add a check in the bisect script that can assign blame to the HIR
optimizer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We will restore this sync target when `lib/pathname.rb` is migrated to `pathname_builtin.rb`
and backport that file to `ruby/pathname` repo.
|
|
https://github.com/rubygems/rubygems/commit/8078a747b3
|
|
Add support for `--zjit-allowed-iseqs=SomeFile` and
`--zjit-log-compiled-iseqs=SomeFile` so we can restrict and inspect
which ISEQs get compiled.
Then add `jit_bisect.rb` which we can run to try and narrow a failing
script. For example:
plum% ../tool/zjit_bisect.rb ../build-dev/miniruby "test.rb"
I, [2025-07-29T12:41:18.657177 #96899] INFO -- : Starting with JIT list of 4 items.
I, [2025-07-29T12:41:18.657229 #96899] INFO -- : Verifying items
I, [2025-07-29T12:41:18.726213 #96899] INFO -- : step fixed[0] and items[4]
I, [2025-07-29T12:41:18.726246 #96899] INFO -- : 4 candidates
I, [2025-07-29T12:41:18.797212 #96899] INFO -- : 2 candidates
Reduced JIT list:
bar@test.rb:8
plum%
We start with 4 compiled functions and shrink to just one.
|
|
Since `RUBY_DESCRIPTION` contains the branch name, `/prism/i` can
match unexpectedly. Extract the feature lists between revision
and platform infos.
|
|
|
|
https://github.com/ruby/fileutils/pull/139
https://github.com/ruby/actions/actions/runs/16425309325/job/46414287784
|
|
|
|
Next version for both will be 4.0.0, however, extra work is necessary to
get CI passing against the new major. So for now, I'm bumping just the
minor version.
|
|
... to conform to UTS 18 as mentioned in https://bugs.ruby-lang.org/issues/19417#note-3
https://unicode.org/reports/tr18/#word states word should match join_control chars.
It currently does not:
```ruby
[*0x0..0xD799, *0xE000..0x10FFFF].map { |n| n.chr 'utf-8' } => all_chars
all_chars.grep(/\p{join_control}/) => jc
jc.count # => 2
jc.grep(/\p{word}/).count # => 0
```
|
|
https://github.com/rubygems/rubygems/commit/afbbc02763
|
|
|
|
gcc master is still using 2021 version files.
|
|
The only use case is access to `repo.or.cz`, and it redirects HTTP
requests to HTTPS now.
|
|
|
|
|
|
Also removed the helper to install real gems during specs to avoid the
temptation of introducing network stuff again.
https://github.com/rubygems/rubygems/commit/a1ab5e319a
|
|
https://github.com/rubygems/rubygems/commit/672722cd4d
|
|
Sync erb.gemspec to under the `lib/erb/ directory.
|
|
They cause flakies when different tests start them in parallel, and also
make the specs more complicated.
|
|
|
|
These files, including `.github` directory, are useless unless the
repository itself is contained as well.
|
|
`executables` are often extracted from the `files` in gemspec files.
|
|
Use the actual files unpacked from the gem. The recent rdoc.gemspec
uses different code than expected by rbinstall.rb, which resulted in
the result list not being overwritten and the template files not being
installed.
|
|
As Set is now a core collection class, it should have special inspect
output. Ideally, inspect output should be suitable to eval, similar
to array and hash (assuming the elements are also suitable to eval):
set = Set[1, 2, 3]
eval(set.inspect) == set # should be true
The simplest way to do this is to use the Set[] syntax.
This deliberately does not use any subclass name in the output,
similar to array and hash. It is more important that users know they
are dealing with a set than which subclass:
Class.new(Set)[]
# this does: Set[]
# not: #<Class:0x00000c21c78699e0>[]
This inspect change breaks the power_assert bundled gem tests, so
add power_assert to TEST_BUNDLED_GEMS_ALLOW_FAILURES in the workflows.
Implements [Feature #21389]
|
|
|
|
|
|
|
|
|
|
- Send outputs from debugger to stderr
- Use `%W` to interpolate the pid
Notes:
Merged: https://github.com/ruby/ruby/pull/13656
|
|
|
|
Ruby HEAD
|
