Issue #19921 has been updated by alanwu (Alan Wu).
Seeing the commit message, what the "& call checks" mean? What makes the failure?
It's the `a & b` call to `Integer#&` in the test. The failure was from a time-based interrupt, which is used for thread switching and for IO operations like stat(2) which `Kernel#require` uses. The test itself shouldn't be doing any IO, but I see that you carry `ruby-2.7.0-Initialize-ABRT-hook.patch`, which makes the VM use `Kernel#require` on boot. That might be the source of the interrupt. This is pure speculation; you can try testing without the patch if you're curious. ---------------------------------------- Bug #19921: TestYJIT#test_bug_19316 test failure https://bugs.ruby-lang.org/issues/19921#change-105040 * Author: vo.x (Vit Ondruch) * Status: Closed * Priority: Normal * Assignee: yjit * ruby -v: ruby 3.3.0dev (2023-10-12 master 52709a4862) [x86_64-linux] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Testing with 52709a4862 on Fedora Rawhide, I observe following failure: ~~~ 94) Failure: TestYJIT#test_bug_19316 [/builddir/build/BUILD/ruby-3.3.0-52709a4862/test/ruby/test_yjit.rb:1126]: Expected no exits, but got {:opt_and=>1} ~~~ -- https://bugs.ruby-lang.org/