Summary: | dev-ruby/thread_safe-0.3.5: segfault during tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Myckel Habets <myckel> |
Component: | [OLD] Development | Assignee: | Gentoo Ruby Team <ruby> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | kingjon3377 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | https://github.com/ruby-concurrency/thread_safe/issues/21 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
build.log of version 0.3.4 build.log of 0.3.6 build.log (0.3.6, ppc) |
Description
Myckel Habets
2013-11-10 19:06:14 UTC
Created attachment 363006 [details]
Build log
Test issues should not block keywording bugs. Could you try again with the latest thread_safe version? I've also seen segmentation faults with other versions, but the latest (0.3.3) passes all tests for me on amd64. Created attachment 380630 [details]
build.log of version 0.3.4
Bug still present in current version.
Reopening. I see this also with thread_safe 0.3.5 but it does not happen consistently. This looks to be a bug in ruby itself: https://bugs.ruby-lang.org/issues/9649 Also happens with 0.3.6 with: ruby 2.3.7p456 (2018-03-28 revision 63024) [hppa2.0-linux] Created attachment 538830 [details]
build.log of 0.3.6
(In reply to Rolf Eike Beer from comment #8) > Also happens with 0.3.6 with: > ruby 2.3.7p456 (2018-03-28 revision 63024) [hppa2.0-linux] Do you trigger this consistently? In any case it is likely that this is a hppa-specific bug. I can't reproduce this on amd64 even with multiple tries. Created attachment 545518 [details]
build.log (0.3.6, ppc)
Same issue on ppc.
dev-ruby/thread_safe-0.3.6 + ruby24 passes all tests on ppc now. |