Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Mon, Dec 28, 2015 at 09:18:04PM +0200, Niko Tyni wrote: > On Mon, Dec 28, 2015 at 04:42:03PM +0100, gregor herrmann wrote: > > Interrupting it in gdb gives this backtrace: > > #0 0x76cc8006 in compress_trie (n=0xa3f2d0) at driver-ti.c:148 > #1 0x76cc8713 in new_driver (tk=,

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Tue, 29 Dec 2015 01:58:51 +0100, gregor herrmann wrote: > > Setting TERM=vt100 seems to not trigger either of these problems, > > so I guess we could try doing that in debian/rules. > Thanks for your further investigation. > Let's do this for now. This seems to have worked quite fine:

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Sun, Dec 27, 2015 at 11:35:48PM -0500, Aaron M. Ucko wrote: > Source: libterm-termkey-perl > Version: 0.16-1 > Severity: serious > Justification: fails to build from source > > Automated builds of libterm-termkey-perl have been failing with errors > of the form > > Test Summary Report >

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Mon, 28 Dec 2015 11:27:25 +0200, Niko Tyni wrote: > I can get this to happen with an unset TERM (on both amd64 and i386). > > Core was generated by `perl -Iblib/lib -Iblib/arch t/05flags.t'. > Program terminated with signal SIGSEGV, Segmentation fault. Same here. Another interesting data

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Mon, Dec 28, 2015 at 04:42:03PM +0100, gregor herrmann wrote: > > I can get this to happen with an unset TERM (on both amd64 and i386). > > > > Core was generated by `perl -Iblib/lib -Iblib/arch t/05flags.t'. > > Program terminated with signal SIGSEGV, Segmentation fault. > > Same here.

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

On Mon, 28 Dec 2015 21:18:04 +0200, Niko Tyni wrote: > > Not sure what to do here. Is there an underlying bug or do we need to > > set TERM to something nice or should we skip the test? > Setting TERM=vt100 seems to not trigger either of these problems, > so I guess we could try doing that in

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

Hi, On Mon, Dec 28, 2015 at 12:06:54AM -0500, Aaron M. Ucko wrote: > Salvatore Bonaccorso writes: > > > Can you please attach the full build log? > > Thanks for the quick reply! The logs are all publically available at >

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

Control: tags -1 + moreinfo Hi Aaron, On Sun, Dec 27, 2015 at 11:35:48PM -0500, Aaron M. Ucko wrote: > Source: libterm-termkey-perl > Version: 0.16-1 > Severity: serious > Justification: fails to build from source > > Automated builds of libterm-termkey-perl have been failing with errors > of

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

Salvatore Bonaccorso writes: > Can you please attach the full build log? Thanks for the quick reply! The logs are all publically available at https://buildd.debian.org/status/package.php?p=libterm-termkey-perl, but for the record, I'm attaching a full copy of the (arm64) log

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

Source: libterm-termkey-perl Version: 0.16-1 Severity: serious Justification: fails to build from source Automated builds of libterm-termkey-perl have been failing with errors of the form Test Summary Report --- t/05flags.t (Wstat: 11 Tests: 2 Failed: 0) Non-zero

Bug#809192: libterm-termkey-perl: FTBFS: 05flags.t: Non-zero wait status: 11

Whoops, I misremembered wget's options. Here's the actual log. Build log for libterm-termkey-perl (0.16-1) on arm64