On Wed, 2022-12-21 at 15:00 -0500, Randy MacLeod wrote: > What tests were you running to check these improvements?
The GNU project doesn't have the resources to perform large-scale testing. We run our regression tests before pushing any code, but that's about all we can manage. The only regular testing we do of -l is to ensure it works (we set the load so low that we're guaranteed to get serialized builds regardless of -j, and make sure that's so). Before pulling these changes in I did some straightforward testing myself, by simply running a large build (GCC IIRC) and verifying, by spot-checking, that we never had too many jobs running. I'm confident I didn't try running multiple disjoint invocations of make in parallel to see what the load was like. I'm always excited to get more testing! Either from the Git repository, or especially during the release candidate cycle: all RC builds are announced on this list and anyone who has the facilities to stress-test the RC builds would be most appreciated!
