| Age | Commit message (Collapse) | Author |
|
These benchmarks should be working fine now.
|
|
|
|
to remind us of skipped benchmarks in the CI job names
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 5.0.0 to 5.0.1.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/a7833574556fa59680c1b7cb190c1735db73ebf0...9255dc7a253b0ccc959486e2bca901246202afeb)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 5.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 5.0.0 to 6.0.0.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](https://github.com/actions/upload-artifact/compare/v5...v6)
---
updated-dependencies:
- dependency-name: actions/upload-artifact
dependency-version: 6.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [msys2/setup-msys2](https://github.com/msys2/setup-msys2) from 2.29.0 to 2.30.0.
- [Release notes](https://github.com/msys2/setup-msys2/releases)
- [Changelog](https://github.com/msys2/setup-msys2/blob/main/CHANGELOG.md)
- [Commits](https://github.com/msys2/setup-msys2/compare/fb197b72ce45fb24f17bf3f807a388985654d1f2...4f806de0a5a7294ffabaff804b38a9b435a73bda)
---
updated-dependencies:
- dependency-name: msys2/setup-msys2
dependency-version: 2.30.0
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 5.0.0 to 5.0.1.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/a7833574556fa59680c1b7cb190c1735db73ebf0...9255dc7a253b0ccc959486e2bca901246202afeb)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 5.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
This reverts commit 1eb10ca3cb6cff98bb8c0946ed905921586c7d52.
This should have been fixed by https://github.com/ruby/ruby/pull/15536.
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 4.3.0 to 5.0.0.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/0057852bfaa89a56745cba8c7296529d2fc39830...a7833574556fa59680c1b7cb190c1735db73ebf0)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 5.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 4.3.0 to 5.0.0.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/0057852bfaa89a56745cba8c7296529d2fc39830...a7833574556fa59680c1b7cb190c1735db73ebf0)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 5.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
and PREVIOUS_RELEASE_TAG for any .0 releases
|
|
|
|
|
|
|
|
|
|
|
|
Mostly YJIT. ZJIT already has the right bindings and this just tweaks
the CI configuration.
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.0 to 6.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/1af3b93b6815bc44a9784bd300feb67ff0d1eeb3...8e8c483db84b4bee98b60c0593521ed34d9990e8)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 6.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.0 to 6.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Commits](https://github.com/actions/checkout/compare/v6...v6.0.1)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 6.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Use the given `make-command` instead of the hard-coded `make` command.
TODO: Use it for `make up` as well, in the future.
|
|
The issue might have been fixed in 8bf333a.
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 5.0.1 to 6.0.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Commits](https://github.com/actions/checkout/compare/v5.0.1...v6)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 6.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 5.0.1 to 6.0.0.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/93cb6efe18208431cddfb8368fd83d5badbf9bfd...1af3b93b6815bc44a9784bd300feb67ff0d1eeb3)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 6.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
`hashFiles` is very unstable on macOS runners.
|
|
clang-18 has a bug that causes ruby_current_ec to sometimes be null when
using Ractors and crashes like this:
<internal:ractor>:700: [BUG] Segmentation fault at 0x0000000000000030
ruby 4.0.0dev (2025-11-21T06:49:14Z master bcc7b2049c) +PRISM [x86_64-linux]
-- Control frame information -----------------------------------------------
c:0004 p:0003 s:0015 e:000014 l:y b:0001 METHOD <internal:ractor>:700
me:
called_id: receive, type: iseq
owner class: 0x00007ff462dda500 T_CLASS/Ractor::Port
self: 0x00007ff46146d068 ractor/port/Ractor::Port ractor/port
c:0003 p:0008 s:0011 e:000010 l:y b:0001 METHOD <internal:ractor>:311
me:
called_id: receive, type: iseq
owner class: 0x00007ff462ddae60 T_CLASS/(anon)
self: 0x00007ff462ddaf00 T_CLASS/Ractor
c:0002 p:0010 s:0007 e:000006 l:n b:---- BLOCK bootstraptest.test_ractor.rb_2354_1323.rb:9 [FINISH]
self: 0x00007ff46146d090 ractor/Ractor r:68
lvars:
j: T_FIXNUM 66
c:0001 p:---- s:0003 e:000002 l:y b:---- DUMMY [FINISH]
self: T_NIL
-- Ruby level backtrace information ----------------------------------------
bootstraptest.test_ractor.rb_2354_1323.rb:9:in 'block (2 levels) in <main>'
<internal:ractor>:311:in 'receive'
<internal:ractor>:700:in 'receive'
-- Threading information ---------------------------------------------------
Total ractor count: 7
Ruby thread count for this ractor: 1
-- Machine register context ------------------------------------------------
RIP: 0x00007ff47c7df5f0 RBP: 0x000055d77ea5b4f0 RSP: 0x00007ff445fa3af0
RAX: 0x0000000000000000 RBX: 0x000055d77e9fd068 RCX: 0x000055d77e9fd040
RDX: 0x000055d77eb2ac40 RDI: 0x00007ff47cbe7700 RSI: 0x0000000000000000
R8: 0x0000000000000000 R9: 0x0000000000000000 R10: 0x000055d77e9fc830
R11: 0x93ba1054e59bfb14 R12: 0x000055d77ea5b4f0 R13: 0x00007ff445f82f20
R14: 0x00007ff4614cf668 R15: 0x000055d77e9fd040 EFL: 0x0000000000010246
-- C level backtrace information -------------------------------------------
libruby.so.4.0(rb_print_backtrace+0x14) [0x7ff47c8cbd18] vm_dump.c:1105
libruby.so.4.0(rb_vm_bugreport) vm_dump.c:1450
libruby.so.4.0(rb_bug_for_fatal_signal+0x162) [0x7ff47c70ce02] error.c:1131
libruby.so.4.0(sigsegv+0x4a) [0x7ff47c82f20a] signal.c:948
/lib/x86_64-linux-gnu/libc.so.6(0x7ff47c34a330) [0x7ff47c34a330]
libruby.so.4.0(rb_ec_thread_ptr+0x0) [0x7ff47c7df5f0] vm_core.h:2092
libruby.so.4.0(rb_ec_ractor_ptr) vm_core.h:2041
libruby.so.4.0(rb_current_execution_context) vm_core.h:2110
libruby.so.4.0(rb_current_ractor_raw) vm_core.h:2109
libruby.so.4.0(rb_current_ractor) vm_core.h:2117
libruby.so.4.0(ractor_unlock) ractor.c:110
libruby.so.4.0(ractor_unlock_self) ractor.c:125
libruby.so.4.0(ractor_wait) ractor_sync.c:1054
libruby.so.4.0(ractor_wait_receive) ractor_sync.c:1113
libruby.so.4.0(ractor_receive+0x25) [0x7ff47c7ded08] ractor_sync.c:1166
libruby.so.4.0(ractor_port_receive) ractor_sync.c:143
libruby.so.4.0(builtin_inline_class_700) ractor.rb:701
libruby.so.4.0(invoke_bf+0x4) [0x7ff47c8a2060] vm_insnhelper.c:7534
libruby.so.4.0(vm_invoke_builtin_delegate) vm_insnhelper.c:0
libruby.so.4.0(vm_exec_core) insns.def:1674
libruby.so.4.0(vm_exec_loop+0x0) [0x7ff47c89b868] vm.c:2784
libruby.so.4.0(rb_vm_exec) vm.c:2787
libruby.so.4.0(vm_invoke_proc+0x344) [0x7ff47c8b03f4] vm.c:1814
libruby.so.4.0(thread_do_start_proc+0x17a) [0x7ff47c870bba] thread.c:593
libruby.so.4.0(thread_do_start+0x162) [0x7ff47c87042f] thread.c:635
libruby.so.4.0(thread_start_func_2) thread.c:686
libruby.so.4.0(rb_native_mutex_lock+0x0) [0x7ff47c870fd1] thread_pthread.c:2238
libruby.so.4.0(thread_sched_lock_) thread_pthread.c:403
libruby.so.4.0(call_thread_start_func_2) thread_pthread_mn.c:466
libruby.so.4.0(co_start) thread_pthread_mn.c:464
|
|
|
|
clang-18 has a bug that causes the latest Ractor btest to crash.
|
|
are changed
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 5.0.0 to 5.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/08c6903cd8c0fde910a37f88322edcfb5dd907a8...93cb6efe18208431cddfb8368fd83d5badbf9bfd)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 5.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 5.0.0 to 5.0.1.
- [Release notes](https://github.com/actions/checkout/releases)
- [Commits](https://github.com/actions/checkout/compare/v5...v5.0.1)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: 5.0.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
This reverts commit 946695cdad874e91bc25bedc3c7b322934ca0f07.
Apparently this doesn't work for test-bundled-gems
|
|
$(RUBY_TESTOPTS) are used in $(TESTOPTS), so if you pass $(TESTOPTS),
it'd be ignored.
|
|
fail-fast is never a good idea for master branch.
|
|
```
Rebasing (1/3)
Committer identity unknown
*** Please tell me who you are.
Run
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
```
|
|
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 5.
- [Release notes](https://github.com/actions/checkout/releases)
- [Commits](https://github.com/actions/checkout/compare/v4...v5)
---
updated-dependencies:
- dependency-name: actions/checkout
dependency-version: '5'
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
It was supposed to update a local branch in case the remote branch was
updated between actions/checkout and the end of tool/sync_default_gems.rb.
Note that this `git pull` didn't exist in the original bin/update-default-gem.sh
https://github.com/ruby/git.ruby-lang.org/commit/d9e9bcc60dcf0dd1cbdc2dd42bc0286439e471aa,
so it was newly introduced at https://github.com/ruby/ruby/commit/3ba5cfd1cb77b61b2b1ad1d03271bc1fe7b71969.
But `git pull --no-ff` failed when master had updates in an unrelated
repository. I think we need to use `git pull --rebase` instead.
This fixes:
* https://github.com/ruby/ruby/actions/runs/19207693793/job/54905403070
* checkout: f08030e9dccf38d9ea5c9505203fe26484dc28d8
* ruby tool/sync_default_gems.rb net-http ec9c70a6fba75a63c128864ef3cb32c883665a33..e4d80bd609f22cad04a2e2c1d54c981bb853c938
* pull: 2bf82c627494e785737037bbaf9a6b98f3c6354c
|
|
|
|
https://github.com/ruby/ruby/actions/runs/19201736990/job/54890646022
|
|
|