-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Artifacts aren't always cleared #53
Comments
Are you able to pop into the machine and run commands interactively? If so, could you run https://github.com/giordano/PkgCleanup.jl to figure out which manifests and artifacts files PkgCleanup thinks are still "active" or "live"? |
It doesn't explain much, because as I mentioned above there's no real Manifest out there. The only one is an ephemeral one that got cleaned during or after the run. I guess that defeats the
I guess we'll have to roll our own mechanism that only considers the artifact folder's
We should always run |
Hmmm, maybe I'm misunderstanding, but if the manifest file is deleted at the end of the CI job, then |
Hmm, that seems correct:
However, I take it that works based off of the |
As observed on
amdci7
, Yggdrasil's build environment, which runs with these pretty vanilla settings: https://github.com/JuliaPackaging/Yggdrasil/blob/6e50b87e3c0e0d289dba12898ee4ceb5b369c446/.buildkite/utils.jl#L33-L37. The depots there get really large, over 500GiB (prompting #52) all in artifacts. However, many of these artifacts are pretty old, and I'd be surprised if they are all used:There is an
artifact_usage.log
in there:... yet Yggdrasil's CI reveals: https://buildkite.com/julialang/yggdrasil/builds/14525#019305f3-fd9e-4b5e-aa12-11c8ce13e03e
Could this be because the
manifest_usage.log
is pointing to nonexisting resources, because those are ephemeral?cc @KristofferC
The text was updated successfully, but these errors were encountered: