Michaël Zasso
Michaël Zasso
https://github.com/nodejs/node/pull/58431
Just want to clarify that I am not actively working on this and do not have the bandwidth at the moment
Did you try `vcbuild.bat noprojgen`? To avoid rerunning the configure script, which may be one of the reasons it recompiles stuff.
It seems to introduce timeouts in other tests.
It seems that the bug is that the web stream doesn't keep a strong reference to the file handle, so that gets garbage collected while it's used.
I don't know if the goal is to land this on v22.x, but it doesn't land cleanly at all.
I'm looking into it
Similar to https://github.com/nodejs/build/issues/3288 I logged into the backup server and ran `/root/backup_scripts/remove_old.sh ci.nodejs.org`. It freed 100GB.
It happened again. @ryanaslett Maybe the new backup server is not setup to run the cleanup script regularly?
In that case, I think the problem is clear. Running `remove_old.sh ci-release.nodejs.org` ends up with an error: ``` # /root/backup_scripts/remove_old.sh ci-release.nodejs.org curl: (92) HTTP/2 stream 1 was not closed cleanly...