Control: tags -1 confirmed -=| gregor herrmann, 30.11.2013 21:17:11 +0100 |=- > On Sat, 30 Nov 2013 17:33:15 +0100, David Suárez wrote: > > > > t/forked1.t ..... ok > > > # Looks like you planned 115 tests but ran 111. > > > print 26175: Connection reset by peer > > > Compilation failed in require at t/forked2.t line 5. > > > t/forked2.t ..... > > > Dubious, test returned 255 (wstat 65280, 0xff00) > > > Failed 4/115 subtests > > Now that's an intereting bug. > The tests still pass for me but take quite some long. So maybe we're > running into a timeout here, or some other fork problem on the amazon > build machine ...
I was able to reproduce this by heavily loading the machine. I used pbzip2 -p16 < $bug file > /dev/null on a 4-core amd64. The tests failed like this: ok 109 # CHILD closing # test paragraph mode, getlines, $/ set funny ok 110 ok 111 # SIGPIPE recevied in 5395 # Looks like you planned 115 tests but ran 111. print 5395: Прекъснат канал Compilation failed in require at t/forked2.t line 5. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 4/115 subtests Test Summary Report ------------------- t/forked2.t (Wstat: 65280 Tests: 111 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 115 tests but ran 111. It is not the same sub-test, suggesting that probably all subtests are fragile on overloaded hosts. Maybe even the whole module is fragile. I'll try to figure out what might be the problem, but my experience with dbd-firebird's fork events tests and arm* doesn't give me high hopes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
