From: utkarsh@debian.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:100293] [Ruby master Bug#17211] Test failures in ruby2.7.2 and ruby3.0~preview1
Date: Sun, 04 Oct 2020 02:17:45 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-87878.20201004021744.44795@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17211.20201002201835.44795@ruby-lang.org
Issue #17211 has been updated by utkarsh (Utkarsh Gupta).
Hey,
mame (Yusuke Endoh) wrote in #note-1:
> Hi, cloud you tell us what environment (OS, distribution, version, CPU, terminal, etc.) you are using? Thanks
Right, sorry for not mentioning this earlier.
I am running Debian Sid. Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz with 16 gigs of RAM (in case that's of any help).
I co-maintain Ruby in Debian and I wanted to upload v2.7.2 but stumbled upon these failures. However, 2.7.1 just builds fine!
Interestingly, I get the same error with 3.0.0~preview1 as well.
Here are the Debina CI logs: https://salsa.debian.org/ruby-team/ruby/-/jobs/1044445#L8148
Please let me know if you need any more information.
----------------------------------------
Bug #17211: Test failures in ruby2.7.2 and ruby3.0~preview1
https://bugs.ruby-lang.org/issues/17211#change-87878
* Author: utkarsh (Utkarsh Gupta)
* Status: Open
* Priority: Normal
* ruby -v: 2.7.2
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
----------------------------------------
Hello,
Whilst building Ruby 2.7.2 and Ruby 3.0~preview1, I got the following test failures:
```
1) Failure:
TestIRB::TestHistory#test_history_save_1 [/<<PKGBUILDDIR>>/test/irb/test_history.rb:31]:
<"exit\n"> expected but was
<"1\n" + "2\n" + "3\n" + "4\n">.
2) Failure:
TestIRB::TestHistory#test_history_save_100 [/<<PKGBUILDDIR>>/test/irb/test_history.rb:51]:
<"1\n" + "2\n" + "3\n" + "4\n" + "5\n" + "exit\n"> expected but was
<"1\n" + "2\n" + "3\n" + "4\n">.
3) Failure:
TestIRB::TestHistory#test_history_save_bignum [/<<PKGBUILDDIR>>/test/irb/test_history.rb:76]:
<"1\n" + "2\n" + "3\n" + "4\n" + "5\n" + "exit\n"> expected but was
<"1\n" + "2\n" + "3\n" + "4\n">.
4) Failure:
TestIRB::TestHistory#test_history_save_minus_as_infinity [/<<PKGBUILDDIR>>/test/irb/test_history.rb:101]:
<"1\n" + "2\n" + "3\n" + "4\n" + "5\n" + "exit\n"> expected but was
<"1\n" + "2\n" + "3\n" + "4\n">.
Finished tests in 424.892771s, 49.5113 tests/s, 6415.2304 assertions/s.
21037 tests, 2725785 assertions, 4 failures, 0 errors, 95 skips
```
I am clueless as to what's causing this?
Please note that I tried to build it in a clean environment. But couldn't get these tests to pass, neither in ruby2.7.2 or ruby3.0~preview1.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2020-10-04 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 20:18 [ruby-core:100284] [Ruby master Bug#17211] Test failures in ruby2.7.2 and ruby3.0~preview1 utkarsh
2020-10-03 4:49 ` [ruby-core:100285] " mame
2020-10-04 2:17 ` utkarsh [this message]
2020-10-04 2:33 ` [ruby-core:100294] " utkarsh
2020-10-04 13:29 ` [ruby-core:100295] " mame
2020-10-04 18:31 ` [ruby-core:100296] " mame
2020-10-05 11:45 ` [ruby-core:100300] " aycabta
2020-10-06 3:36 ` [ruby-core:100306] " utkarsh
2020-10-07 17:47 ` [ruby-core:100334] " merch-redmine
2020-10-11 6:42 ` [ruby-core:100369] " nagachika00
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-87878.20201004021744.44795@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).