ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "hs (Hideki Sakamoto) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hs (Hideki Sakamoto)" <noreply@ruby-lang.org>
Subject: [ruby-core:120716] [Ruby master Bug#18613] Voluntary wanted: Some signal-related tests fail on FreeBSD 13
Date: Thu, 16 Jan 2025 15:34:06 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-111549.20250116153405.18@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-18613.20220308072905.18@ruby-lang.org>

Issue #18613 has been updated by hs (Hideki Sakamoto).

File patch-test_io_console_test__io__console.rb added
File patch-test_ruby_test__thread__queue.rb added
File patch-test_ruby_test__thread.rb added

I apologize if my comment on the closed ticket is inappropriate. By the way, these bugs seem to have been fixed in FreeBSD 13.4 (or 13.3).

I applied the attached patch to the Ruby 3.4.1 source and tried "make test-all" dozens of times in FreeBSD 13.4(while checking #21045), but the error no longer reappeared.

<pre>
% tar xf ruby-3.4.1.tar.xz
% cd ruby-3.4.1/
% patch < patch-test_io_console_test__io__console.rb
% patch < patch-test_ruby_test__thread.rb
% patch < patch-test_ruby_test__thread__queue.rb
% ./configure
% make
% make test-all
</pre>

While not a direct reference, a bug report similar to this bug has been reported in FreeBSD Bugzilla – [Bug 277429](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277429)  and appears to have been fixed in 13.3.


----------------------------------------
Bug #18613: Voluntary wanted: Some signal-related tests fail on FreeBSD 13
https://bugs.ruby-lang.org/issues/18613#change-111549

* Author: mame (Yusuke Endoh)
* Status: Feedback
* Assignee: knu (Akinori MUSHA)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
Some tests fail randomly on FreeBSD 13.

http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220216T143001Z.fail.html.gz

```
  1) Error:
TestThread#test_signal_at_join:
Timeout::Error: execution of assert_separately expired timeout (120 sec)
pid 30743 killed by SIGABRT (signal 6) (core dumped)
| 

    /usr/home/chkbuild/chkbuild/tmp/build/20220216T143001Z/ruby/test/ruby/test_thread.rb:1390:in `test_signal_at_join'
```

http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220308T023001Z.fail.html.gz

```
  1) Failure:
TestThreadQueue#test_thr_kill [/usr/home/chkbuild/chkbuild/tmp/build/20220308T023001Z/ruby/test/ruby/test_thread_queue.rb:175]:
only 169/250 done in 60 seconds.
```

http://rubyci.s3.amazonaws.com/freebsd13/ruby-master/log/20220304T163001Z.fail.html.gz

```
  1) Failure:
TestIO_Console#test_intr [/usr/home/chkbuild/chkbuild/tmp/build/20220304T163001Z/ruby/test/io/console/test_io_console.rb:387]:
<"25"> expected but was
<"-e:12:in `p': \e[1mexecution expired (\e[1;4mTimeout::Error\e[m\e[1m)\e[m">.
```

All of the tests is related to signals. I guess something around signals has changed in FreeBSD 13, but I'm unsure. The failure occurs at high frequency in CI, but rarely does on my FreeBSD shell. We need to investigate what happens.

@knu is the platform maintainer for FreeBSD but he is busy. Contribution who is familiar with FreeBSD is welcome.

To make it easy to monitor the CI results, I tentatively skipped the three tests on FreeBSD https://github.com/ruby/ruby/commit/17e09f033c4d3b786672ba16d2c5d935482a2fad . If you investigate the issue on FreeBSD, please delete test/excludes/TestThread.rb and test/excludes/TestThreadQueue.rb, and remove the guard in test/io/console/test_io_console.rb.

---Files--------------------------------
patch-test_io_console_test__io__console.rb (508 Bytes)
patch-test_ruby_test__thread__queue.rb (276 Bytes)
patch-test_ruby_test__thread.rb (337 Bytes)


-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/

      parent reply	other threads:[~2025-01-16 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  7:29 [ruby-core:107790] " mame (Yusuke Endoh)
2022-05-30  1:43 ` [ruby-core:108735] " mame (Yusuke Endoh)
2025-01-16 15:34 ` hs (Hideki Sakamoto) via ruby-core [this message]

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-all from there: mbox

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

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

  git send-email \
    --in-reply-to=redmine.journal-111549.20250116153405.18@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@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 NNTP newsgroup(s).