This is an auto-filed bug because dev-ruby/minitest-bonus-assertions fails tests. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: If you need further logs, feel free to ask.
Created attachment 640298 [details] build.log build log and emerge --info
Seem to have the same with -r1. >>> Test phase: dev-ruby/minitest-bonus-assertions-3.0-r1 * Running test phase for ruby27 ... Run options: --seed 47492 # Running: ...............F.......F............. Finished in 0.044873s, 824.5468 runs/s, 2094.7947 assertions/s. 1) Failure: Minitest::BonusAssertions::.assert_missing_keys#test_0001_returns true if the keys are missing [/var/tmp/portage/dev-ruby/minitest-bonus-assertions-3.0-r1/work/ruby27/minitest-bonus-assertions-3.0/test/test_minitest-bonus-assertions.rb:139]: returns true for key 'b' missing from { 'a' => 1 }. Expected: false Actual: true 2) Failure: Minitest::BonusAssertions::.refute_set_equal#test_0001_returns true if the sets are not equal [/var/tmp/portage/dev-ruby/minitest-bonus-assertions-3.0-r1/work/ruby27/minitest-bonus-assertions-3.0/test/test_minitest-bonus-assertions.rb:215]: returns true for sets %w(a b c) and %w(c b). Expected: true Actual: false 37 runs, 94 assertions, 2 failures, 0 errors, 0 skips * ERROR: dev-ruby/minitest-bonus-assertions-3.0-r1::gentoo failed (test phase): * (no error message) * * Call stack: * ebuild.sh, line 127: Called src_test * environment, line 2141: Called ruby-ng_src_test * environment, line 1802: Called _ruby_each_implementation 'each_ruby_test' * environment, line 531: Called _ruby_invoke_environment 'ruby27' 'each_ruby_test' * environment, line 656: Called each_ruby_test * environment, line 877: Called die * The specific snippet of code: * ${RUBY} -Ilib:.:test -e 'Dir["test/test_*.rb"].each{|f| require f}' || die
Can we restrict tests here given upstream looks pretty dead? It makes automating stabilisation a pain otherwise.
(In reply to Sam James from comment #3) > Can we restrict tests here given upstream looks pretty dead? It makes > automating stabilisation a pain otherwise. I can't reproduce these test failures, so something else must be going on.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6caa712078c8bdea4e978a7356f7304871c2addd commit 6caa712078c8bdea4e978a7356f7304871c2addd Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2022-05-26 07:16:49 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2022-05-26 07:17:49 +0000 dev-ruby/minitest-bonus-assertions: avoid broken tests Two tests are flaky and randomly fail for different people. Closes: https://bugs.gentoo.org/723928 Signed-off-by: Hans de Graaff <graaff@gentoo.org> .../minitest-bonus-assertions-3.0-r1.ebuild | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)