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

2020-12-12 Thread Michael Biebl
Am 12.12.20 um 10:12 schrieb Lucas Nussbaum: On 11/12/20 at 15:08 +0100, Michael Biebl wrote: https://github.com/systemd/systemd-bootchart/pull/37 specifically https://github.com/systemd/systemd-bootchart/pull/37/commits/65320230f5fcb02e81df5131a4dc03092558c263 Could you give this PR a try?

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

2020-12-12 Thread Lucas Nussbaum
On 11/12/20 at 15:08 +0100, Michael Biebl wrote: > Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: > > On 10/12/20 at 22:12 +0100, Michael Biebl wrote: > > > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: > > > > Hi Michael! > > > > > > > > On 12/10/20 8:42 PM, Michael Biebl wrote: > > > >

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

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: On 10/12/20 at 22:12 +0100, Michael Biebl wrote: 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

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

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 13:45 +0100, Michael Biebl wrote: > Am 11.12.20 um 09:26 schrieb Lucas Nussbaum: > > I tried to reproduce this on another system (ARM64, 256 visible cores > > because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also > > segfaults. > > > > I tried to reproduce on yet another

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

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 13:42 +0100, Michael Biebl wrote: > Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: > > 0x00014d04 in svg_ps_bars (interval=, > > graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, > > n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187 > >

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

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:26 schrieb Lucas Nussbaum: I tried to reproduce this on another system (ARM64, 256 visible cores because 2 x ThunderX2, 32 cores/cpu, 4 threads/core) and it also segfaults. I tried to reproduce on yet another system (x86_64, 128 visible cores because 4x Intel Xeon Gold 6130,

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

2020-12-11 Thread Michael Biebl
Am 11.12.20 um 09:09 schrieb Lucas Nussbaum: 0x00014d04 in svg_ps_bars (interval=, graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187 looking at n_cpus=1, what's the output of /proc/schedstat?

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

2020-12-11 Thread Lucas Nussbaum
On 10/12/20 at 22:12 +0100, Michael Biebl wrote: > 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

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

2020-12-11 Thread Lucas Nussbaum
On 11/12/20 at 09:09 +0100, Lucas Nussbaum wrote: > On 10/12/20 at 22:12 +0100, Michael Biebl wrote: > > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz: > > > Hi Michael! > > > > > > On 12/10/20 8:42 PM, Michael Biebl wrote: > > > >

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

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

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

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

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

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

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

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

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

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

2020-12-09 Thread 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 packages in sid, your package failed to build on ppc64el. At the same time, it did not fail on