severity 1100201 serious thanks [ Gianfranco, please always Cc me on the bugs I report if you talk to me in your replies. You already should know that the BTS does not forward messages to the submitter ]
I suspect this has to do with parallelism of your build server, can you please try to lower it or to increase the timeout?
I tried building the package on machines with 1 CPU and 2 CPUs. A lot of times. The failure rate was 93% and 23% respectively, neither of which can be considered suitable for release. I can't reduce parallelism more than having a single CPU, and I don't think whoever wants to build the package from source should have to jump through hoops to build the package without errors. If there is a test which is flaky, please disable it. A test which fails when it should not fail is more harmful than useful. Also, I included this text in my bug report that you missed completely:
If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible.
The offer still holds, but I recommend that you try GRUB_CMDLINE_LINUX="nr_cpus=1" first. Thanks.
