[Bug 992723] perl-Sys-SigAction: FTBFS in rawhide

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=992723

Paul Howarth <paul(a)city-fan.org&gt; changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
                 CC|                            |paul(a)city-fan.org
   Fixed In Version|                            |perl-Sys-SigAction-0.20-1.f
                   |                            |c20
         Resolution|---                         |RAWHIDE
           Assignee|andreas(a)bawue.net           |paul(a)city-fan.org
        Last Closed|                            |2013-08-05 06:43:23



--- Comment #1 from Paul Howarth <paul(a)city-fan.org&gt; ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=tMG2E3EZae&a=cc_unsubscribe