| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
from ruby/git.ruby-lang.org as of:
https://github.com/ruby/git.ruby-lang.org/commit/b0dfa734297cc9aea33f24a1e29f8853cc5761e9
|
|
The 2 issues that we applied the workarounds for were fixed now.
|
|
https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/
|
|
Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.4.2 to 2.4.3.
- [Release notes](https://github.com/ossf/scorecard-action/releases)
- [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md)
- [Commits](https://github.com/ossf/scorecard-action/compare/05b42c624433fc40578a4040d5cf5e36ddca8cde...4eaacf0543bb3f2c246792bd56e8cdeffafb205a)
---
updated-dependencies:
- dependency-name: ossf/scorecard-action
dependency-version: 2.4.3
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
I forgot that this step existed and thought crash reporting wasn't
working when they were simply moved to a different step. Failing these
should give a nice visual hint.
|
|
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 4.2.4 to 4.3.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/0400d5f644dc74513175e3cd8d07132dd4860809...0057852bfaa89a56745cba8c7296529d2fc39830)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 4.3.0
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
It probably doesn't need to run for topic branches created by
dependabot, and it's also likely annoying in stable branches like
ruby_X_Y too.
|
|
which was broken by 9255db4bc08766763a6d78f50a90e05c58980899
|
|
Add `make-ibm` job to run ppc64le/s390x cases in the `ubuntu.yml`, and remove
`ubuntu-ibm.yml`. This commit improves removing a duplicated logic between the
`ubuntu.yml` and `ubuntu-ibm.yml`.
I am using the YAML anchors and aliases feature to avoid the duplicated logic.
The document is below.
https://docs.github.com/en/actions/reference/workflows-and-actions/reusing-workflow-configurations#yaml-anchors-and-aliases
I don't add the `make-ibm` job to the `result` job, the line `needs: [make]`
intentionally to make the `make-ibm` job's result optional to merge PRs.
|
|
|
|
Bumps [lewagon/wait-on-check-action](https://github.com/lewagon/wait-on-check-action) from 1.4.0 to 1.4.1.
- [Release notes](https://github.com/lewagon/wait-on-check-action/releases)
- [Changelog](https://github.com/lewagon/wait-on-check-action/blob/master/CHANGELOG.md)
- [Commits](https://github.com/lewagon/wait-on-check-action/compare/0dceb95e7c4cad8cc7422aee3885998f5cab9c79...3603e826ee561ea102b58accb5ea55a1a7482343)
---
updated-dependencies:
- dependency-name: lewagon/wait-on-check-action
dependency-version: 1.4.1
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
Fixes https://github.com/Shopify/ruby/issues/758
|
|
* Comment on not auto-requesting reviews for workflow files
* Make it easier to reproduce matrix test_task commands from CI
Expand the interpolated command so that it is easier to see exactly what command was run.
|
|
We sometimes see silent crashes on CI such as
<https://github.com/ruby/ruby/actions/runs/17661854762/job/50196469793>.
The default of dumping to stderr could be interacting poorly
with the parallel workers, so let's use RUBY_CRASH_REPORT to hopefully
get more information.
|
|
ubuntu-24.04-arm jobs look working as of 2025-09-16.
|
|
These tests are run in the dedicated workflows for JITs.
|
|
Now it is always compiled (and will be optimized away).
|
|
|
|
* Release builds depend only on `rustc` for sake of packaging. Removing
it from the image ensures that passing the CI implies that only `rustc`
is required.
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 9d0b621b051c0f3cc356c9bedf081456f1d7dfd6.
It didn't work for `make check`. I'll fix it in a PR.
|
|
ref: https://github.com/ruby/ruby/pull/14459
|
|
|
|
Bumps [actions/github-script](https://github.com/actions/github-script) from 7.0.1 to 8.0.0.
- [Release notes](https://github.com/actions/github-script/releases)
- [Commits](https://github.com/actions/github-script/compare/60a0d83039c74a4aee543508d2ffcb1c3799cdea...ed597411d8f924073f98dfc5c65a23a2325f34cd)
---
updated-dependencies:
- dependency-name: actions/github-script
dependency-version: 8.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 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>
|
|
ZJIT, YJIT: Make the workflow names consistent
with file names
|
|
|
|
|
|
|
|
Set the runner user's primary group to avoid a mismatch between the group IDs of
"id -g" and C function getpwuid(uid_t uid) pw_gid in a test as a better
workaround.
|
|
|
|
They don't start at all and they get cancelled.
https://github.com/ruby/ruby/actions/runs/17476949351/job/49639049451
To unblock PR merges, let's disable it until it's fixed.
|
|
|
|
|
|
This commit fixes the failures in bootstraptest/test_ractor.rb reported on
the issue ticket <https://bugs.ruby-lang.org/issues/21534>.
TLS (Thread-Local Storage) may not be accessed across .so on ppc64le too.
I am not sure about that. The comment "// TLS can not be accessed across
.so on ..." in this commit comes from the following commit.
https://github.com/ruby/ruby/commit/319afed20fba8f9b44611d16e4930260f7b56b86#diff-408391c43b2372cfe1fefb3e1c2531df0184ed711f46d229b08964ec9e8fa8c7R118
> // on Darwin, TLS can not be accessed across .so`
This failures only happened when configuring with cppflags=-DRUBY_DEBUG and -O3
on ppc64le.
The reproducing steps were below.
```
$ ./autogen.sh
$ ./configure -C --disable-install-doc cppflags=-DRUBY_DEBUG
$ make -j4
$ make btest BTESTS=bootstraptest/test_ractor.rb
...
FAIL 2/147 tests failed
make: *** [uncommon.mk:913: yes-btest] Error 1
```
The steps with a reproducing script based on the `bootstraptest/test_ractor.rb`
were below.
```
$ cat test_ractor_1.rb
counts = []
counts << Ractor.count
p counts.inspect
ractors = (1..2).map { Ractor.new { Ractor.receive } }
counts << Ractor.count
p counts.inspect
ractors[0].send('End 0').join
sleep 0.1 until ractors[0].inspect =~ /terminated/
counts << Ractor.count
p counts.inspect
ractors[1].send('End 1').join
sleep 0.1 until ractors[1].inspect =~ /terminated/
counts << Ractor.count
p counts.inspect
$ make run TESTRUN_SCRIPT=test_ractor_1.rb
...
vm_core.h:2017: Assertion Failed: rb_current_execution_context:ec == rb_current_ec_noinline()
...
```
The assertion failure happened at the following line.
https://github.com/ruby/ruby/blob/f3206cc79bec2fd852e81ec56de59f0a67ab32b7/vm_core.h#L2017
This fix is similar with the following commit for the arm64.
https://github.com/ruby/ruby/commit/f7059af50a31a4d27a04ace0beadb60616f3f971
Fixes [Bug #21534]
|
|
|
|
Bumps [msys2/setup-msys2](https://github.com/msys2/setup-msys2) from 2.28.0 to 2.29.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/40677d36a502eb2cf0fb808cc9dec31bf6152638...fb197b72ce45fb24f17bf3f807a388985654d1f2)
---
updated-dependencies:
- dependency-name: msys2/setup-msys2
dependency-version: 2.29.0
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
https://github.com/ruby/ruby/actions/runs/17308244022/job/49136485007
I'm not sure if it's stuck forever at the end or happens to take that
much time around the end of it, but let me just try this first.
If it doesn't work, something's wrong with --repeat-count=2 on test-all.
|