| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
|
|
Note that the default configure option `./configure cppflags=-DRUBY_DEBUG` with
the default optimization level `-O3`, causes the following Ractor test and other
tests failing. So, we don't set the option in ppc64le case.
```
$ make btest BTESTS=bootstraptest/test_ractor.rb
```
See https://bugs.ruby-lang.org/issues/21534 for details.
|
|
* Remove logic that was used for the ubuntu.yml, but not used for
ubuntu-ibm.yml.
* Add a dummy Ubuntu x86_64 case to make this CI pass on fork repositories.
This case only runs on fork repositories.
|
|
This reverts commit c3c74e0d31c0c7327d2eb2c79b253d6500c6f2c0.
|
|
We are seeing the not-starting s390x jobs.
Until the following issue is fixed, we drop the s390x case.
https://github.com/IBM/actionspz/issues/34
|
|
* cp ubuntu.yml ubuntu-ibm.yml
* Revert "CI: ubuntu.yml: Skip user ground id test on ppc64le and s390x"
This reverts commit 9fa87a668836f83ab836d0cbcefb4056622a0ed6.
* Revert "CI: ubuntu.yml: Set HOME env on ppc64le and s390x"
This reverts commit 05b654b43f6d0e92fbc3e1e908d811f031d59e40.
* Revert "CI: ubuntu.yml: Add GitHub Actions s390x case"
This reverts commit 099df0b40b215b2fc5db59569d45c59ee48111a7.
* Remove duplication among copied jobs
|
|
Bumps [lewagon/wait-on-check-action](https://github.com/lewagon/wait-on-check-action) from 31f07a800aa1ba8518509dc8561cdf5a891deb4b to 0dceb95e7c4cad8cc7422aee3885998f5cab9c79.
- [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/31f07a800aa1ba8518509dc8561cdf5a891deb4b...0dceb95e7c4cad8cc7422aee3885998f5cab9c79)
---
updated-dependencies:
- dependency-name: lewagon/wait-on-check-action
dependency-version: 0dceb95e7c4cad8cc7422aee3885998f5cab9c79
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps [actions/cache](https://github.com/actions/cache) from 4.2.3 to 4.2.4.
- [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/5a3ec84eff668545956fd18022155c47e93e2684...0400d5f644dc74513175e3cd8d07132dd4860809)
---
updated-dependencies:
- dependency-name: actions/cache
dependency-version: 4.2.4
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
|
|
|
|
At under a minute, this check runs faster than a lot of the other CI
checks, so we might as well show errors from `cargo check` to serve as a
smoke check in addition to surfacing warnings.
|
|
|
|
|
|
This is a temporary workaround.
|
|
This is a temporary workaround.
|
|
Add the s390x case using GitHub Actions ppc64le/s390x service.
https://github.com/IBM/actionspz
We can run the ppc64le/s390x cases only in the registered upstream repositories.
https://github.com/IBM/actionspz/blob/main/docs/FAQ.md#what-about-forked-repos
The following matrix upstream logic is to skip the ppc64le/s390x in the
downstream (fork) repositories.
```
+ upstream:
+ - ${{ github.repository == 'ruby/ruby' }}
```
Use the "os" list to determine the excluded ppc64le/s390x cases by using the
"exclude" syntax. Because the "exclude" syntax are executed before the
"include" syntax.
Add the ubuntu-24.04-ppc64le as a comment, because the GitHub Actions ppc64le
case has the following test errors and failures.
https://bugs.ruby-lang.org/issues/21534
|
|
Rust PRs will have a failed CI step if they trigger any warnings.
This helps us stay on top of warnings from new Rust releases and
also ones we accidentally write.
Fix a typo for demo, since this only runs when Rust files are changed.
|
|
Saves the work of installing Rust for most jobs. Keep a job on each
platform that tests 1.85.0, the minimum supported version, though.
|
|
Because ruby/setup-ruby is affected to test result.
|
|
|
|
It is used in more steps than `sh`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since `RUBY_DESCRIPTION` contains the branch name, `/prism/i` can
match unexpectedly. Extract the feature lists between revision
and platform infos.
|
|
|
|
|
|
After several ZJIT fix PRs, the number of failing/crashing tests for
ZJIT has dropped significantly. This removes the unneeded test exclusions.
|
|
ZJIT: run zjit-test-all on CI with seed
ZJIT is still unstable and can crash intermittently running with Ruby
tests. Adding a seed to avoid flakiness while we work on stability.
|
|
testing targets/docs (#13791)
* ZJIT: Add test exclusions for ZJIT
* ZJIT: Update test targets and documentation
- Rename `zjit-test-all` to `zjit-check`
- Add `zjit-test-all` target to zjit.mk to run all Ruby tests with ZJIT enabled
excluding known failing tests
- Update documentation and CI workflow to reflect the new targets
|
|
It is already a bundled gem, and only the non-built-in parts remain in
pathname.rb in ./lib and cannot work in old versions.
|
|
vcpkg cache
|
|
* ZJIT: Avoid optimizing locals on eval
* Maintain the local state for eval
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* ZJIT: Stop tracking EP == BP assumption on JIT entry
* Enable test_method.rb as well
|
