ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: aycabta@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:100300] [Ruby master Bug#17211] Test failures in ruby2.7.2 and ruby3.0~preview1
Date: Mon, 05 Oct 2020 11:45:39 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-87888.20201005114539.44795@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-17211.20201002201835.44795@ruby-lang.org

Issue #17211 has been updated by aycabta (aycabta .).


I decided to stop using `system` method for E2E testing because it depends on `ruby` command. I'm sorry for the rough implementation.

https://github.com/ruby/ruby/pull/3628

This patch of this Pull Request resolves the failure of CI.

----------------------------------------
Bug #17211: Test failures in ruby2.7.2 and ruby3.0~preview1
https://bugs.ruby-lang.org/issues/17211#change-87888

* Author: utkarsh (Utkarsh Gupta)
* Status: Assigned
* Priority: Normal
* Assignee: aycabta (aycabta .)
* 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/

  parent reply	other threads:[~2020-10-05 11:45 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 ` [ruby-core:100293] " utkarsh
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 ` aycabta [this message]
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-87888.20201005114539.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).