Based on the discussion below we should look at the disk space thresholds that jenkins uses before bringing machines offline. It looks from the message referenced below that the threshold was about 200MB which is far less than the 3-4GB used for a single additional extract. We should revisit that figure to ensure that in a heavy load scenario jenkins can take the machine offline before it causes a problem in the jobs.
@sxa unfortunately this has taken test-mnx-ubuntu2204-x64-1 offline in Jenkins:
It is also causing git checkout failures, e.g. https://ci.nodejs.org/job/node-test-commit-plinux/65613/console
...
Resolving deltas: 100% (861498/861498), done.
fatal: sha1 file '.git/objects/pack/tmp_idx_BwgFWa' write error: Disk quota exceeded
fatal: fetch-pack: invalid index-pack output
...
Originally posted by @richardlau in #6556
Based on the discussion below we should look at the disk space thresholds that jenkins uses before bringing machines offline. It looks from the message referenced below that the threshold was about 200MB which is far less than the 3-4GB used for a single additional extract. We should revisit that figure to ensure that in a heavy load scenario jenkins can take the machine offline before it causes a problem in the jobs.
Originally posted by @richardlau in #6556