From: mame@... Date: 2019-11-26T14:16:51+00:00 Subject: [ruby-core:95962] [Ruby master Bug#16361] TestEnv#test_fetch failure Issue #16361 has been updated by mame (Yusuke Endoh). So are you running just `make test-all` normally? I misguessed that you reconstructed the tarball for rpm package or something. Sorry. I have never seen the issue in CIs (I may overlook of course), and we have no such a report against preview3. I've run the following but cannot reproduce the issue. ``` $ wget https://cache.ruby-lang.org/pub/ruby/snapshot.tar.gz $ tar xf snapshot.tar.gz $ cd snapshot $ ./configure && make -j && make test-all ``` ---------------------------------------- Bug #16361: TestEnv#test_fetch failure https://bugs.ruby-lang.org/issues/16361#change-82796 * Author: vo.x (Vit Ondruch) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.7.0dev (2019-11-22 master f9d20a1bf1) [x86_64-linux] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- I am facing following test suite error: ~~~ 1) Failure: TestEnv#test_fetch [/builddir/build/BUILD/ruby-2.7.0-f9d20a1bf1/test/ruby/test_env.rb:123]: [ruby-core:56062] [Feature #8649]. Expected Exception(KeyError) was raised, but the message doesn't match. <"key not found: \"test\""> expected but was <"key not found: \"test\"\n" + "Did you mean? \"TESTS\"">. ~~~ Trying to execute this test independently, it passes just fine. So it seems that the did_you_mean gem is loaded unexpectedly on this place. I just tried: ~~~ mv test/optparse/test_did_you_mean.rb{,.bak} ~~~ since this is the latest addition IMO and the test suite passes just fine. I am not really sure why it should fail on my setup and it probably does not fail in any other CI. Neither I am sure what would be the best option to fix this. The assertion could be updated to accept this message by simple sed: ~~~ sed -i "/'key not found: \"test\"'/ s/'/\//g" test/ruby/test_env.rb ~~~ -- https://bugs.ruby-lang.org/ Unsubscribe: