------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_libressl-abi32+64_20170706-192148 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.3.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.4.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm
Created attachment 481632 [details] emerge-info.txt
Created attachment 481634 [details] dev-perl:AnyEvent-7.130.0:20170707-122643.log
Created attachment 481636 [details] emerge-history.txt
Created attachment 481638 [details] environment
Created attachment 481640 [details] etc.portage.tbz2
Created attachment 481642 [details] temp.tbz2
t/80_ssltest.t ............. 1/415 t/80_ssltest.t ............. Failed 414/415 subtests Test Summary Report ------------------- t/80_ssltest.t (Wstat: 11 Tests: 1 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 415 tests but ran 1. Files=82, Tests=251, 29 wallclock secs ( 0.26 usr 0.11 sys + 2.23 cusr 0.36 csys = 2.96 CPU)
Can you see if this is reproducible on AnyEvent-7.140.0 just shipped to tree? I saw some patches land with regards to signals and SSL. Ideally, you'll want to run *just* AnyEvent with: DIST_TEST_OVERRIDE="do verbose" In your environment. ( This is *not* safe to do generically as it vetoes the tests defaults )
(In reply to Kent Fredric (IRC: kent\n) from comment #8) Oh, the tinderbox already picked them up (b/c an added/changed/modified/erased ebuild) - and seems, the tests are passed fine now :-)
Marking as fixed in 7.140.0 Reopen if you can get a detailed reproduction.