From: "Eregon (Benoit Daloze) via ruby-core" Date: 2025-04-30T19:20:19+00:00 Subject: [ruby-core:121785] [Ruby Bug#21295] macos-13 debug build failures Issue #21295 has been updated by Eregon (Benoit Daloze). It failed again: https://github.com/ruby/ruby-dev-builder/actions/runs/14739297053/job/41404925541 ``` 1) Error: TestWeakKeyMap#test_clear_bug_20691: Test::Unit::ProxyError: execution of Test::Unit::CoreAssertions#assert_normal_exit expired timeout (10 sec) pid 47217 killed by SIGTERM (signal 15) | /Users/runner/work/ruby-dev-builder/ruby-dev-builder/test/ruby/test_weakkeymap.rb:65:in 'TestWeakKeyMap#test_clear_bug_20691' 2) Error: TestObjSpace#test_trace_object_allocations_compaction_freed_pages: Test::Unit::ProxyError: execution of Test::Unit::CoreAssertions#assert_normal_exit expired timeout (10 sec) pid 57011 killed by SIGTERM (signal 15) | /Users/runner/work/ruby-dev-builder/ruby-dev-builder/test/objspace/test_objspace.rb:311:in 'TestObjSpace#test_trace_object_allocations_compaction_freed_pages' Finished tests in 801.448522s, 34.5761 tests/s, 7557.8192 assertions/s. 27711 tests, 6057203 assertions, 0 failures, 2 errors, 115 skips ``` And passed in the [latest build](https://github.com/ruby/ruby-dev-builder/actions/runs/14762324952/job/41445762135). So these looks to me like transient tests (potentially just not long enough timeout) and for some reason they seem to happen somewhat more on macos-13 / darwin-amd64. But `TestTracepointObj#test_teardown_with_active_GC_end_hook` mentioned above is specific to debug builds. ---------------------------------------- Bug #21295: macos-13 debug build failures https://bugs.ruby-lang.org/issues/21295#change-112843 * 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/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/