Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 992723
Summary: | perl-Sys-SigAction FTBFS: t/nested.t segfaults on ARM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dennis Gilmore <dennis> |
Component: | perl-Sys-SigAction | Assignee: | Andreas Thienemann <andreas> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 24 | CC: | andreas, paul, perl-devel, ppisar |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | armv7hl | ||
OS: | Unspecified | ||
URL: | http://koschei.cloud.fedoraproject.org/package/perl-Sys-SigAction | ||
Whiteboard: | |||
Fixed In Version: | perl-Sys-SigAction-0.20-1.fc20 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-08 11:42:45 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 245418 |
Description
Dennis Gilmore
2013-08-05 05:57:53 UTC
Seems to be an intermittent fault in t/nested.t: $ make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/mask.t ..... ok t/name.t ..... ok t/nested.t ... Failed 4/4 subtests t/number.t ... ok NOTE: Setting safe=>1... with masked signals does not seem to work. The problem is that the masked signals are not masked when safe=>1. When safe=>0 they are. If you have an application for safe=>1 and can come up with a test that works in the context of this module's installation please send me a patch to safe.t that tests it. See the block below this one... which if executed would test safe mode with masked signals... it is a clone of part of mask.t that proves this is broken. Lincoln t/safe.t ..... ok # delta time was 0.100351, timer was for 0.1 secconds t/timeout.t .. ok Test Summary Report ------------------- t/nested.t (Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 4 tests but ran 0. Files=6, Tests=40, 9 wallclock secs ( 0.12 usr 0.03 sys + 0.91 cusr 0.11 csys = 1.17 CPU) Result: FAIL I tried the latest upstream version and it worked for me locally and in a koji scratch build so I updated it in git... and my first build attempt failed the same way. I tried again and it worked. This issue may turn up again in future but for the time being we can concentrate on other FTBFS packages. It always fails on ARM. It passes on other supported platforms. Because this is noarch package, it looks like a random failure. See <http://koschei.cloud.fedoraproject.org/package/perl-Sys-SigAction>. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Upstream will simplify the failing test. It will not fail. It's probably a bug in perl/glibc/kernel, but because the original test so complicated, nobody cannot create a simple reproducer. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |