Closed alanshaw closed 5 years ago
Still happening today :(
Fixed the script to not fail entirely if it fails to delete one directory (seems gx is keeping itself running at some points). Works better now.
There is a separate issue on Windows workers only though, as it seems the cleanWS
function doesn't really delete the files as it does on macOS and Linux workers. Will be looking into that closer.
FYI, a while ago I made changes to js-ipfs to clean up after itself to help alleviate this problem, but for failures and timeouts it might not cleanup.
Really, I think we don't want any state hanging around on the machines from prior runs. It would be nice if the machine could just be reset to a given state for each run.
I also got Error: ENOSPC: no space left on device, write
on Windows:
Not sure why, Companion's Jenkinsfile should do cleanup at the end, even on error:
} finally {
cleanWs()
}
Did it run out of space due to an other project/issue or is cleanWs()
not as effective as I assumed?
Still an issue? Consolidate with the CI exploration on ipfs/infra?
I am quite sure @victorb squashed this specific one (some temp files were not cleared properly on Windows).
Which Project is this about?
Jenkins CI
Provide a link to a example run where it went wrong
https://ci.ipfs.team/view/System/job/clean-workspaces/
Which platform did the issue happen on?
Windows