Issue #21295 has been updated by Eregon (Benoit Daloze). MSP-Greg (Greg L) wrote:
ruby/ruby-dev-builder cannot update any master build if one or more of the master builds fail.
Feel free to file that as an issue at https://github.com/ruby/setup-ruby. I disabled issues for ruby/*-dev-builder because I want to avoid an explosion of number of issue trackers. But in short it works as designed (and I don't see any solution): we should not publish releases without all builds otherwise it will break setup-ruby for the missing builds. It's also not good to use a debug build from an older commit and a regular build from a newer commit, they should always match. The assumption is CRuby core cares about keeping RUBY_DEBUG builds green, since in fact they asked to add it (and if they would no longer then we should remove `ruby-debug` in setup-ruby, we're not there). ---------------------------------------- Bug #21295: ruby/ruby-dev-builder - macos-13 debug build failures, stops GHA master build updates https://bugs.ruby-lang.org/issues/21295#change-112837 * Author: MSP-Greg (Greg L) * Status: Open * ruby -v: master * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- @Eregon [ruby/ruby-dev-builder](https://github.com/ruby/ruby-dev-builder) has issues turned off, which I can understand. It is the repo that creates the Ubuntu & macOS MRI master/head builds used in GHA (GitHub Actions). Recently, there have been test-all failures in the 'macos-13 debug' job. Also, the tests take longer to run than macos-14. I believe macos-13 is x64, macos-14 is arm64. It would certainly be nice to fix the problem. In at least a few workflow runs, it is the only job failure. A more significant issue is that any failure in the workflow's jobs stops a new release from being created. The 'macos-13 debug' jobs have failed on the last two days runs (it . Recently `Set` was updated, I believe it's been a few days, but I don't recall any API changes. I believe no tests were changed/added, but marshalling set was covered in test suites. Hence, that was overlooked, and a subsequent PR/commit fixed it. But, the first commit was done where a new release was created. Since the the 2nd commit was done, all the 'macos-13 debug' jobs have been failing. Hence, it's not available in GHA. So, there are two issues: 1. 'macos-13 debug' is failing test-all 2. ruby/ruby-dev-builder cannot update any master build if one or more of the master builds fail. -- https://bugs.ruby-lang.org/