Re: [OT] Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8(i386/1 cpu)

2011-04-22 Thread Dr.Ruud
On 2011-04-21 08:59, Jesse Vincent wrote: ./Confiure Srawberry? -- Ruud

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-20 Thread Jesse Vincent
I built both 5.14.0-RC1 and 5.12.3 on a completely vanilla OpenBSD 4.8. ./Confiure -Dusethreads -des I used this test script: require POSIX; use Test::More tests => 1; my $new = POSIX::SigSet->new(&POSIX::SIGUSR1); POSIX::sigprocmask(&POSIX::SIG_BLOCK, $new); my $gotit

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-20 Thread Leon Timmermans
On Wed, Apr 20, 2011 at 5:06 PM, Leon Timmermans wrote: > Ugh, portable signal handling really does suck balls. I really don't > have the time to look deeply into this right now, but I would suggest > someone to port the test in question to C (should be fairly > straightforward) and try to run it.

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-20 Thread Leon Timmermans
On Tue, Apr 12, 2011 at 11:13 PM, Dave Mitchell wrote: > This test has been hanging the test script on openbsd and mirbsd > since it was added with commit 0c1bf4c7d433bb0ad80bfe5511b1301db32b7b95. > > The test in question does: > >    require POSIX; >    my $new = POSIX::SigSet->new(&POSIX::SIGUSR

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-13 Thread Tony Cook
On Wed, Apr 13, 2011 at 07:19:40PM +0100, Nicholas Clark wrote: > On Tue, Apr 12, 2011 at 10:13:49PM +0100, Dave Mitchell wrote: > > This test has been hanging the test script on openbsd and mirbsd > > since it was added with commit 0c1bf4c7d433bb0ad80bfe5511b1301db32b7b95. > > > so somehow the si

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-13 Thread Nicholas Clark
On Tue, Apr 12, 2011 at 10:13:49PM +0100, Dave Mitchell wrote: > This test has been hanging the test script on openbsd and mirbsd > since it was added with commit 0c1bf4c7d433bb0ad80bfe5511b1301db32b7b95. > so somehow the signal gets lost rather than just being temporarily blocked. > Does anyone w

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-04-12 Thread Dave Mitchell
On Fri, Mar 25, 2011 at 08:49:15PM +0100, Steven Schubiger wrote: > Craig A. Berry wrote: > > Got any details on that? Any chance it was caused by something recent > > from this list: > > http://refcnt.homeunix.org/smoke/p5openbsd/511x/log5da6b59a91ad9679bcad4cba7615c78cd63d09f8.log > > $ ./per

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-03-25 Thread Craig A. Berry
On Fri, Mar 25, 2011 at 11:40 AM, Steven Schubiger wrote: > Automated smoke report for 5.13.11 patch > 5da6b59a91ad9679bcad4cba7615c78cd63d09f8 v5.13.11-190-g5da6b59 > p5openbsd: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2 > cache) (909 MHz) (i386/1 cpu) >    on        openbsd -

Re: Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-03-25 Thread Steven Schubiger
Craig A. Berry wrote: > Got any details on that? Any chance it was caused by something recent > from this list: http://refcnt.homeunix.org/smoke/p5openbsd/511x/log5da6b59a91ad9679bcad4cba7615c78cd63d09f8.log $ ./perl -MTestInit t/op/sigdispatch.t 1..15 ok 1 - before the first loop o

Smoke [5.13.11] v5.13.11-190-g5da6b59 FAIL(F) openbsd 4.8 (i386/1 cpu)

2011-03-25 Thread Steven Schubiger
Automated smoke report for 5.13.11 patch 5da6b59a91ad9679bcad4cba7615c78cd63d09f8 v5.13.11-190-g5da6b59 p5openbsd: AMD Athlon(tm) Processor ("AuthenticAMD" 686-class, 256KB L2 cache) (909 MHz) (i386/1 cpu) onopenbsd - 4.8 using cc version 4.2.1 20070719 smoketime 17 hours