reopen 1103358 thanks
retitle 1103358 make max-parallel more accurate and verbose
thanks
On 4/17/25 10:07, Lucas Nussbaum wrote:
Actually it already failed twice on that system, because in my archive
rebuilds I retry failures automatically to be able to ignore random
failures.
wow, cool feature - didn't know.
But I tried it again on a larger VM (32 GB, 8 cores) and it succeeded.
So let's close it, and I'll switch to that larger VM for future
rebuilds.
thanks for checking.
Let's keep the bug open until:
* I have the "new" simplified max-parallel calculation uploaded. my
hunch is that the current 4gb/core is to good to be true due to
additional overhead consumption.
* Additionally I ment to add a "information output" during the build
where it lists number of cores, ram size and the calculated
max-parallel so that these things can be spottet with less
roundtrips directly from the build log.
I plan do to that for the 18.2.5 point-release update (which currently
FTBFS for other reasons and has two regressions that need fixing over
18.2.4, sigh).
Regards,
Daniel
