ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: mame@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95914] [Ruby master Bug#16361] TestEnv#test_fetch failure
Date: Sat, 23 Nov 2019 00:34:05 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-82754.20191123003404.4b418da17d5928a9@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16361.20191122143512@ruby-lang.org

Issue #16361 has been updated by mame (Yusuke Endoh).


How did you run the test?  Currently, bundled gems should be unavailable in `make test-all`, and some tests don't assume that bundled gems are loaded.

Currently, did_you_mean is a bundled gem, so should not be loaded in `make test-all`.  [test/optparse/test_did_you_mean.rb](https://github.com/ruby/ruby/blob/818708edab6e950a8c1828816b73d36f05585f9f/test/optparse/test_did_you_mean.rb#L3) is disabled in effect: `require "did_you_mean" rescue return`.  So this test file should not be loaded in the whole test suite run.

We plan to convert did_you_mean to a default gem.  Until the conversion, the test file will be disabled.

----------------------------------------
Bug #16361: TestEnv#test_fetch failure
https://bugs.ruby-lang.org/issues/16361#change-82754

* 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/

  parent reply	other threads:[~2019-11-23  0:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-16361.20191122143512@ruby-lang.org>
2019-11-22 14:35 ` [ruby-core:95911] [Ruby master Bug#16361] TestEnv#test_fetch failure v.ondruch
2019-11-23  0:34 ` mame [this message]
2019-11-23 20:20 ` [ruby-core:95916] " v.ondruch
2019-11-24 14:08 ` [ruby-core:95924] " mame
2019-11-26  8:05 ` [ruby-core:95953] " v.ondruch
2019-11-26 14:16 ` [ruby-core:95962] " mame
2019-12-09 12:50 ` [ruby-core:96161] " v.ondruch
2019-12-09 12:54 ` [ruby-core:96162] " v.ondruch
2019-12-09 12:57 ` [ruby-core:96163] " v.ondruch
2020-01-08 15:35 ` [ruby-core:96713] " v.ondruch
2020-01-08 22:06 ` [ruby-core:96717] " mame

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-82754.20191123003404.4b418da17d5928a9@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).