Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
On Fri, 05 Jan 2018 22:54:08 +0200, Niko Tyni wrote: > > t/66_ioasync_02_signals.t or t/66_ioasync_03_child.t? > t/66_ioasync_03_child.t, I think. See below. Cool. > > Anyway, IIRC we've seen failures in different tests over time. > That's what I thought too but didn't find much at least > in the buildd logs. Ack, my search in recent logs also defeated my memory :) > > On > > https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.140-1=1505267718=0 > > Bailout called. Further testing stopped: No child exit detected. This is > > either a bug in AnyEvent or a bug in your Perl (mostly some windows > > distributions suffer from that): child watchers might not work properly on > > this platform. You can force installation of this module if you do not rely > > on child watchers, or you could upgrade to a working version of Perl for > > your platform. > > (Does this mean that t/66_ioasync_02_signals.t failed or the > > following t/66_ioasync_03_child.t ?) > I think it comes from the 'Bail out! No child exit detected' part in > t/66_ioasync_03_child.t. Presumably the test libraries are buffering > parts of the output. Thanks, this was my assumption as well. > So I guess this all boils down to the (sort of documented) "issues > with IO::Async", at least until we see other failures. Agreed. > > Commit pushed to alioth, feedback welcome before I upload. > LGTM, thanks! Thanks for checking! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
On Fri, Jan 05, 2018 at 02:35:38AM +0100, gregor herrmann wrote: > On Mon, 01 Jan 2018 18:56:52 +0200, Niko Tyni wrote: > > Disregarding hurd-i386, the problematic test seems to be > > t/66_ioasync_03_signals.t, > > t/66_ioasync_02_signals.t or t/66_ioasync_03_child.t? t/66_ioasync_03_child.t, I think. See below. > Anyway, IIRC we've seen failures in different tests over time. That's what I thought too but didn't find much at least in the buildd logs. > > I'm not sure what to make of this. Maybe disarm this particular test somehow > > for now and see how it fares otherwise? > On > https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.140-1=1505267718=0 > Bailout called. Further testing stopped: No child exit detected. This is > either a bug in AnyEvent or a bug in your Perl (mostly some windows > distributions suffer from that): child watchers might not work properly on > this platform. You can force installation of this module if you do not rely > on child watchers, or you could upgrade to a working version of Perl for your > platform. > > (Does this mean that t/66_ioasync_02_signals.t failed or the > following t/66_ioasync_03_child.t ?) I think it comes from the 'Bail out! No child exit detected' part in t/66_ioasync_03_child.t. Presumably the test libraries are buffering parts of the output. > Looks like t/66_ioasync_03_child.t is our candidate, if I'm > interpreting this correctly. Agreed. > Oh, and I have another hang on my Raspi: Awesome, thanks for testing. So I guess this all boils down to the (sort of documented) "issues with IO::Async", at least until we see other failures. > Commit pushed to alioth, feedback welcome before I upload. LGTM, thanks! -- Niko
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
On Mon, 01 Jan 2018 18:56:52 +0200, Niko Tyni wrote: > The issue seems mostly specific to armel and hurd, although > tests.reproducible-builds.org does have some failures on i386 (but no > logs so those could be just testbed glitches or transient sid issues.) > I don't know what happened in Ubuntu but it clearly built later. Yup, it seems a bit undeterministic. > Currently we have a build failure on armel that's blocking testing > migration of this package. Given the number of reverse dependencies, > I suppose we need to solve this one way or other. Ack. > Disregarding hurd-i386, the problematic test seems to be > t/66_ioasync_03_signals.t, t/66_ioasync_02_signals.t or t/66_ioasync_03_child.t? Anyway, IIRC we've seen failures in different tests over time. > which is using AnyEvent::Impl::IOAsync > which uses IO::Async. Ack, that's the whole t/66_ioasync_*.t block. > I see the AnyEvent::Impl::IOAsync docs have some > reservations about IO::Async, this in particular: That, and more comments in the code and documentation about IO::Async. > I'm not sure what to make of this. Maybe disarm this particular test somehow > for now and see how it fares otherwise? Which one exactly? :) I tend to disable the whole t/66_ioasync_*.t group. Or maybe not: And, lo and behold, I could reproduce a test failure, on one of my raspis, running Raspbian Buster (and under some load). There the test suite was just hanging here: t/66_ioasync_03_child.t 1..50 ok 1 ok 2 # child 15124 ok 3 # 15124 == 15124 ok 4 # 3 == 768 >> 8 (768) ok 5 # 15126 == 15126 ok 6 # 7 == 1792 >> 8 (1792) ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 # child 15127 Of course this only happened once over the time I run the tests in a loop so far ... On https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.140-1=1505267718=0 it was t/66_ioasync_02_signals.t .. 1..5 ok 1 ok 2 ok 3 ok 4 ok 5 ok Bailout called. Further testing stopped: No child exit detected. This is either a bug in AnyEvent or a bug in your Perl (mostly some windows distributions suffer from that): child watchers might not work properly on this platform. You can force installation of this module if you do not rely on child watchers, or you could upgrade to a working version of Perl for your platform. (Does this mean that t/66_ioasync_02_signals.t failed or the following t/66_ioasync_03_child.t ?) Some other failures: https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.120-1%2Bb1=1474787791=0 https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=armel=7.120-1%2Bb1=1474805578=0 same as above https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=sparc64=7.130-1=1476943760=0 t/66_ioasync_02_signals.t .. 1..5 ok 1 ok 2 ok 3 ok 4 ok 5 ok E: Caught signal ‘Terminated’: terminating immediatelydebian/rules:13: recipe for target 'override_dh_auto_test' failed So basically the same. https://buildd.debian.org/status/fetch.php?pkg=libanyevent-perl=x32=7.070-3=1411189350=0 t/66_ioasync_02_signals.t .. ok Bailout called. Further testing stopped: No child exit detected. This is either a bug in AnyEvent or a bug in your Perl (mostly some windows distributions suffer from that): child watchers might not work properly on this platform. You can force installation of this module if you do not rely on child watchers, or you could upgrade to a working version of Perl for your platform. Same again. Looks like t/66_ioasync_03_child.t is our candidate, if I'm interpreting this correctly. Oh, and I have another hang on my Raspi: t/66_ioasync_03_child.t 1..50 ok 1 ok 2 # child 22400 ok 3 # 22400 == 22400 ok 4 # 3 == 768 >> 8 (768) ok 5 # 22401 == 22401 ok 6 # 7 == 1792 >> 8 (1792) ok 7 ok 8 ok 9 ok 10 ok 11 ok 12 # child 22402 ok 13 # 22402 == 22402 ok 14 # 3 == 768 >> 8 (768) ok 15 # 22403 == 22403 ok 16 # 7 == 1792 >> 8 (1792) ok 17 ok 18 ok 19 ok 20 ok 21 ok 22 # child 22404 ok 23 # 22404 == 22404 ok 24 # 3 == 768 >> 8 (768) ok 25 # 22405 == 22405 ok 26 # 7 == 1792 >> 8 (1792) ok 27 ok 28 ok 29 ok 30 ok 31 ok 32 # child 22406 ok 33 # 22406 == 22406 ok 34 # 3 == 768 >> 8 (768) ok 35 # 22407 == 22407 ok 36 # 7 == 1792 >> 8 (1792) ok 37 ok 38 ok 39 ok 40 ok 41 ok 42 # child 22408 Commit pushed to alioth, feedback welcome before I upload. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: STS: Großvater signature.asc Description: Digital Signature
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
On Wed, Sep 13, 2017 at 04:45:39PM +0200, gregor herrmann wrote: > On Sun, 17 Aug 2014 00:10:04 -0700, gregor herrmann wrote: > > On Fri, 06 Jun 2014 12:42:08 +0200, gregor herrmann wrote: > > > > > libanyevent-perl sometimes has test failures in different tests on > > > different architectures. > > > I also had one locally (on amd64) once which went away in later > > > rebuilds ... > > > > > > Looks quite random :/ > On Ubuntu, the build failed everywhere: > https://launchpad.net/ubuntu/+source/libanyevent-perl/7.140-1 > > On Debian only on armel (and hurd): > https://buildd.debian.org/status/logs.php?pkg=libanyevent-perl=7.140-1 > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libanyevent-perl.html > (amd64 only so far) and https://ci.debian.net/packages/liba/libanyevent-perl/ > (amd64 only so far) look good. > > This looks all quite random. CPAN RT and cpantesters also don't show > anything obvious … The failing tests are conditional on the PERL_ANYEVENT_LOOP_TESTS environmental variable, so it's no wonder cpantesters doesn't help. The issue seems mostly specific to armel and hurd, although tests.reproducible-builds.org does have some failures on i386 (but no logs so those could be just testbed glitches or transient sid issues.) I don't know what happened in Ubuntu but it clearly built later. Currently we have a build failure on armel that's blocking testing migration of this package. Given the number of reverse dependencies, I suppose we need to solve this one way or other. Disregarding hurd-i386, the problematic test seems to be t/66_ioasync_03_signals.t, which is using AnyEvent::Impl::IOAsync which uses IO::Async. I see the AnyEvent::Impl::IOAsync docs have some reservations about IO::Async, this in particular: When you develop your program on FreeBSD and run it on GNU/Linux, you might have unpleasant surprises, as IO::Async::Loop will by default use IO::Async::Loop::Epoll, which is incompatible with "fork", so your network server will run into spurious and very hard to debug problems under heavy load, as IO::Async forks a lot of processes, e.g. for DNS resolution. It would be better if IO::Async would only load "safe" backends by default (or fix the epoll backend to work in the presence of fork, which admittedly is hard - EV does it for you, and also does not use unsafe backends by default). I'm not sure what to make of this. Maybe disarm this particular test somehow for now and see how it fares otherwise? -- Niko Tyni nt...@debian.org
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
Control: found -1 7.140-1 Control: severity -1 serious Control: tag -1 + buster sid On Sun, 17 Aug 2014 00:10:04 -0700, gregor herrmann wrote: > Control: severity -1 important > > On Fri, 06 Jun 2014 12:42:08 +0200, gregor herrmann wrote: > > > libanyevent-perl sometimes has test failures in different tests on > > different architectures. > > I also had one locally (on amd64) once which went away in later > > rebuilds ... > > > > Looks quite random :/ > > > > For 7.070-2 cf. > > https://buildd.debian.org/status/logs.php?pkg=libanyevent-perl=7.070-2 > > The 5.20 binNMUs built everywhere again, so lowering severity to > important. And the problems are back with 7.140-1. On Ubuntu, the build failed everywhere: https://launchpad.net/ubuntu/+source/libanyevent-perl/7.140-1 On Debian only on armel (and hurd): https://buildd.debian.org/status/logs.php?pkg=libanyevent-perl=7.140-1 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libanyevent-perl.html (amd64 only so far) and https://ci.debian.net/packages/liba/libanyevent-perl/ (amd64 only so far) look good. This looks all quite random. CPAN RT and cpantesters also don't show anything obvious … Cheers, gregor -- .''`. https://info.comodo.priv.at/ - Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Eric Clapton: Swing Low Sweet Chariot signature.asc Description: Digital Signature
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
Control: severity -1 important On Fri, 06 Jun 2014 12:42:08 +0200, gregor herrmann wrote: libanyevent-perl sometimes has test failures in different tests on different architectures. I also had one locally (on amd64) once which went away in later rebuilds ... Looks quite random :/ For 7.070-2 cf. https://buildd.debian.org/status/logs.php?pkg=libanyevent-perlver=7.070-2 The 5.20 binNMUs built everywhere again, so lowering severity to important. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#750732: libanyevent-perl: Intermittent build failures on various architectures
Source: libanyevent-perl Version: 7.070-2 Severity: serious Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 libanyevent-perl sometimes has test failures in different tests on different architectures. I also had one locally (on amd64) once which went away in later rebuilds ... Looks quite random :/ For 7.070-2 cf. https://buildd.debian.org/status/logs.php?pkg=libanyevent-perlver=7.070-2 Cheers, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJrBAEBCgBVBQJTkZsAThSAAB0AKGlzc3Vlci1mcHJAZ3BnLmNvbW9kby5w cml2LmF0RDFFMTMxNkU5M0E3NjBBODEwNEQ4NUZBQkIzQTY4MDE4NjQ5QUEwNgAK CRC7OmgBhkmqBpFrD/4jj+Iif6qC0Rr3pljL27fXMuEOTPV2/Sd5Aoy1mIrH0syv C8OoQKATaRZ/DbAEruRH+9ITunvyZx2IU92xbZjNL/PeQvREuKejsZ1YdKaF698v TQy5oIXvg7p6A6IX95tZ4cCDF2g+4zYlp3YsIIyL5AwZkG4eXWHjHUymXSlxsvZt ajxjWXRe1Jot1tSXmRb3DiQ3b6Soti+SDbGJoGpIZg9evEMe+c+prdGcCA+pDXGM aaw4nWt4zpz246N6GbVZXzfH9TrZlXxP/+3uOKokzskyjQawK1zhjL9IAq6Q8Vho 2iG4T3WQxPlUxPUCRqTyiFCK21DXfD9P1BavrG50UoDzBKC3ltz5LxVbKu+klEvj aiWHg+L6Ia3B9TTaAyQjFSvUfTU0u9AU4Gci7xmHiK/ksKGvWvYhgpKd00+s7Lf5 m0S2mGFHqZgo1qgUwKLj3xFbKY6oVCtMik0hbaXRiddKz4eI1qbLPhabUScrPXJz iM0X6pOEtszWSscNHXg6a50g9M4iAsgJXqCY+1G8YmjCcIk/OI1chejyqkwWn4S+ uEhOdX4pAt6/Gq15d0Z9gUe/z0A6xTK2FXdLnxXuwDcLbsluu6zxUR1IW/pbCVum N58ZeYfB2X7vz4+a0EFlRMw/kGUU/yMc5/x8uTla/OIjhDCJLM4BBXB66N/LJw== =rCup -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
