[#114348] [Ruby master Feature#19832] Method#destructive?, UnboundMethod#destructive? — "sawa (Tsuyoshi Sawada) via ruby-core" <ruby-core@...>

Issue #19832 has been reported by sawa (Tsuyoshi Sawada).

15 messages 2023/08/06

[#114365] [Ruby master Bug#19834] Segmentation fault while running in docker — "ramachandran@... (Ramachandran A) via ruby-core" <ruby-core@...>

Issue #19834 has been reported by ramachandran@mallow-tech.com (Ramachandran A).

7 messages 2023/08/09

[#114380] [Ruby master Bug#19837] Concurrent calls to Process.waitpid2 misbehave on Ruby 3.1 & 3.2 — "kjtsanaktsidis (KJ Tsanaktsidis) via ruby-core" <ruby-core@...>

Issue #19837 has been reported by kjtsanaktsidis (KJ Tsanaktsidis).

7 messages 2023/08/11

[#114399] [Ruby master Feature#19839] Need a method to check if two ranges overlap — "shouichi (Shouichi KAMIYA) via ruby-core" <ruby-core@...>

Issue #19839 has been reported by shouichi (Shouichi KAMIYA).

27 messages 2023/08/18

[#114410] [Ruby master Bug#19841] Marshal.dump stack overflow with recursive Time — "segiddins (Samuel Giddins) via ruby-core" <ruby-core@...>

Issue #19841 has been reported by segiddins (Samuel Giddins).

9 messages 2023/08/18

[#114422] [Ruby master Feature#19842] Intorduce M:N threads — "ko1 (Koichi Sasada) via ruby-core" <ruby-core@...>

Issue #19842 has been reported by ko1 (Koichi Sasada).

30 messages 2023/08/21

[#114590] [Ruby master Bug#19857] Eval coverage is reset after each `eval`. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19857 has been reported by ioquatix (Samuel Williams).

21 messages 2023/08/30

[ruby-core:114470] [Ruby master Bug#14474] skip "TestException#test_thread_signal_location" as known bug

From: "jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@...>
Date: 2023-08-23 20:11:02 UTC
List: ruby-core #114470
Issue #14474 has been updated by jeremyevans0 (Jeremy Evans).

Status changed from Open to Closed

This test has not been skipped since commit:5ec3450438150e7cb05422c04dc18901161a13ea in January 2022, and I don't think this has been a problem since, so I'm closing this.

----------------------------------------
Bug #14474: skip "TestException#test_thread_signal_location" as known bug
https://bugs.ruby-lang.org/issues/14474#change-104243

* Author: ko1 (Koichi Sasada)
* Status: Closed
* Priority: Normal
* ruby -v: 2.6
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
`TestException#test_thread_signal_location` fails randomly

https://gist.github.com/ko1/797b0f058f2d09ae57c9af1ee07a42b2#file-brlog-trunk-nopara-20180213-224440-L380
> `[BUG] pthread_mutex_lock: Invalid argument (EINVAL)`

https://gist.github.com/ko1/df41bb11a19792a14417c9332e70171e#file-brlog-trunk-asserts-nopara-20180213-081040-L438
> `[BUG] Segmentation fault at 0x0000000000000000`

and so on.

This test consists of signal, threads, termination process, and so on.
I've tried to investigate but no idea. Additionally, it is hard to reproduce.

To keep CI clean, I skip this test, file about this issue and wait for a person who can solve this issue.

Thanks,
Koichi



-- 
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/postorius/lists/ruby-core.ml.ruby-lang.org/

In This Thread

Prev Next