From: "alanwu (Alan Wu) via ruby-core" Date: 2023-10-19T21:09:44+00:00 Subject: [ruby-core:115109] [Ruby master Bug#19921] TestYJIT#test_bug_19316 test failure Issue #19921 has been updated by alanwu (Alan Wu). Could someone kick off a Koji build with commit:9047fe5ea4e8c989c1081aa10f741a413c546534 "YJIT: Print exit reasons on failure in test_yjit.rb"? It adds some extra information to the failure message that should resolve this mystery. This will likely be the last run we need to spend on this issue and is mostly for my own curiosity. The failing test is fine with the exit; merely checking that the result is good enough (see [ruby-core:112973] from 7 months ago). Regardless of the outcome of the Koji attempt, we'll put `exits: :any` on the test in a day or so to resolve this issue. [ruby-core:112973]: https://bugs.ruby-lang.org/issues/19316#note-11 ---------------------------------------- Bug #19921: TestYJIT#test_bug_19316 test failure https://bugs.ruby-lang.org/issues/19921#change-105016 * Author: vo.x (Vit Ondruch) * Status: Feedback * 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/ ______________________________________________ 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/postorius/lists/ruby-core.ml.ruby-lang.org/