reopen 1108341
thanks

>    * Running test-suite single threaded on all architectures (Closes:
>      #1108341).

Hello.

Sorry for the reopening, but I believe this is not fixed yet.

This package used to FTBFS in my setup, on machines with 2 CPUs,
approximately 10% the time. The autobuilder hang happens in a way
that it has to be killed by hand. Not even sbuild's built-in
timeout mechanism works.

Now I've tried to build 0.7.2-7 a lot of times (25) and I got two hangs,
so the failure rate remains more or less the same, and the bug I
initially reported ("random hang on machines with 2 CPUs") is not fixed.


Unfortunately, there is more: The previous version used to build
flawlessly on machines with 1 CPU, but now this is what happens
when I try the same:

----[ Testing barrier....
make[4]: Entering directory '/<<PKGBUILDDIR>>/regressions/ck_barrier/validate'
rc=0;                                                   \
for d in barrier_centralized barrier_combining barrier_dissemination 
barrier_tournament barrier_mcs ; do              
                  \
        echo $d;                                        \
        ./$d 2 1 1 || rc=1;                     \
done;                                                   \
exit $rc
barrier_centralized
Creating threads (barrier)...done
Waiting for threads to finish correctness regression...WARNING: Could not 
affine thread: Invalid argument
E: Build killed with signal TERM after 10 minutes of inactivity


I tried 25 times and it failed 25 times. If you want to reproduce
this, the easy way is to tell grub via GRUB_CMDLINE_LINUX="nr_cpus=1",
but if you prefer a VM, contact me privately and I will gladly provide one.

In summary, the bug I reported is not fixed, and now the package always
fails on machines with 1 CPU. I would say that version -6 was better.

Thanks.

Reply via email to