Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread Lucas Nussbaum
Hi, On 10/12/20 at 22:16 +0100, John Paul Adrian Glaubitz wrote: > Hi! > > On 12/10/20 10:12 PM, Michael Biebl wrote: > >> Did the test machine you used actually have that many cores? > > > > No idea > > I just checked plummer.debian.org and it has only 16 (virtual) CPUs. > > Would be curious

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread John Paul Adrian Glaubitz
On 12/10/20 10:16 PM, Michael Biebl wrote: >>> Did the test machine you used actually have that many cores? >> >> No idea > > But given that there is only a single test, I wonder if that is really > relevant anyway. You're right. That's rather strange. Hmm. Adrian -- .''`. John Paul Adrian

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread Michael Biebl
Am 10.12.20 um 22:12 schrieb Michael Biebl: Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: Testsuite summary for systemd-bootchart 233 =

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread John Paul Adrian Glaubitz
Hi! On 12/10/20 10:12 PM, Michael Biebl wrote: >> Did the test machine you used actually have that many cores? > > No idea I just checked plummer.debian.org and it has only 16 (virtual) CPUs. Would be curious to hear whether Lucas' test machine had >= 160 CPUs. Adrian -- .''`. John Paul Ad

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread Michael Biebl
Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: Testsuite summary for systemd-bootchart 233

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread John Paul Adrian Glaubitz
Hi Michael! On 12/10/20 8:42 PM, Michael Biebl wrote: > > Testsuite summary for systemd-bootchart 233 > > # TOTAL: 1 > # PASS: 1 > # SKIP: 0 >

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread Michael Biebl
Am 10.12.20 um 20:18 schrieb John Paul Adrian Glaubitz: Hi Michael! On 12/10/20 7:53 PM, Michael Biebl wrote: Unfortunately, I can't reproduce the issue on a porter box (plummer). So I'm not sure if I can do something about it. It might be an issue with parallel jobs as Lucas built the packag

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread John Paul Adrian Glaubitz
Hi Michael! On 12/10/20 7:53 PM, Michael Biebl wrote: > Unfortunately, I can't reproduce the issue on a porter box (plummer). > So I'm not sure if I can do something about it. It might be an issue with parallel jobs as Lucas built the package with make -j160 and some packages can't cope with that

Re: Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

2020-12-10 Thread Michael Biebl
Control: tags -1 + unreproducible Hello Lucas Am 09.12.20 um 09:42 schrieb Lucas Nussbaum: Source: systemd-bootchart Version: 233-2 Severity: serious Justification: FTBFS on ppc64el Tags: bullseye sid ftbfs Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el Hi, During a rebuild of all pack

Re: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-10 Thread Mathieu Malaterre
"make -j160" that would be my guess :) remove parallel from the dh option, and try again (fixes symptoms) On Thu, Dec 10, 2020 at 10:49 AM Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > I tried to investigate the situation below and my guess is that lex has > somehow problems to cre

Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

2020-12-10 Thread Andreas Tille
Control: tags -1 help Hi, I tried to investigate the situation below and my guess is that lex has somehow problems to create the missing header files. I've found the files in upstreams .gitignore file so these need to be created but this does not seem to work on ppc64el (any more - since the pac