This bug appears to have been fixed in July.

remake: 5.8.4-4, failed (12 test failures)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-4&arch=mipsel&stamp=1099771004&file=log&as=raw
remake: 5.8.4-4, failed (12 test failures)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-4&arch=mipsel&stamp=1101291814&file=log&as=raw

repeat.rfc822.org: 5.8.4-5, failed (12 test failures)
        Presumably the same machine as remake...
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-5&arch=mipsel&stamp=1102820411&file=log&as=raw
remake: 5.8.4-5, failed (12 test failures)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-5&arch=mipsel&stamp=1103895333&file=log&as=raw

solitude: 5.8.4-6, success
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-6&arch=mipsel&stamp=1107362357&file=log&as=raw

remake: 5.8.4-7, failed (outlier?)
        Errno architecture (mipsel-linux-thread-multi-2.4.27-sb1-swarm-bn) does
        not match executable architecture
        (mipsel-linux-thread-multi-2.4.20-pre6) at /usr/lib/perl/5.8/Errno.pm
        line 11.
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-7&arch=mipsel&stamp=1110208039&file=log&as=raw

remake: 5.8.4-8, failed (12 test failures)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-8&arch=mipsel&stamp=1110314271&file=log&as=raw
solitude: 5.8.4-8, success
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.4-8&arch=mipsel&stamp=1110579504&file=log&as=raw

(Presumably remake was rebuilt and became rem here?)

rem: 5.8.7-2, failed (only one test, t/op/fork, failed)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-2&arch=mipsel&stamp=1118196397&file=log&as=raw

rem: 5.8.7-3, success
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-3&arch=mipsel&stamp=1118273494&file=log&as=raw

rem: 5.8.7-4, failed (only one test, t/op/fork, failed)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-4&arch=mipsel&stamp=1120885183&file=log&as=raw
rem: 5.8.7-4, failed (only one test, t/op/fork, failed)
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-4&arch=mipsel&stamp=1121067847&file=log&as=raw
rem: 5.8.7-4, success
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-4&arch=mipsel&stamp=1121104986&file=log&as=raw

rem: 5.8.7-5, success
http://buildd.debian.org/fetch.php?&pkg=perl&ver=5.8.7-5&arch=mipsel&stamp=1126486805&file=log&as=raw

So it appears to me that this FTBFS bug filed against remake can be
closed, as the machine in question has been either rebuilt or retired.

I haven't actually done anything to this bug as there may be more going
on here than I'm aware of, but from what I can see this isn't a bug in
perl, but an issue with the buildd that has since been solved.

(If remake and repeat are seperate machines, then there's at least
something repeatable across machines here.)

If it was/is an issue with the buildd, then the 12-test failure first
appears in 5.8.4-2.2 on 2004-09-07, and last appears 2005-03-08, and the
t/op/fork test failure first appears 2005-06-07 and was last seen
2005-07-11 (and a rebuild 10 hours later on the same machine didn't
fail, so if this was an issue, it may have been fixed that day?)

(The 12 tests failing earlier don't include t/op/fork, BTW)

-- 
Paul "TBBle" Hampson, [EMAIL PROTECTED]
8th year CompSci/Asian Studies student, ANU

Shorter .sig for a more eco-friendly paperless office.

Attachment: pgpa7RDzkcgzV.pgp
Description: PGP signature

Reply via email to