Staging fails with "Could not find file at ..."
Summary
Sometimes (I suspect when cache cleaning happens) some files disappear from the cache, and buildstream builds just fail afterwards.
Steps to reproduce
I don't have a clear way to reproduce, but I have
- default config for buildstream
- no remote artifact caches
and I'm using buildstream normally to build elements.
What is the current bug behavior?
At some point (probably when cache is full) some files disappear from beneath buildstream's feet (I guess cleaned by buildbox-casd), and buildstream cannot recover. It doesn't detect that the artifact is incomplete (and thus invalid); neither in the same session, nor in a subsequent session.
What is the expected correct behavior?
Ideally, it shouldn't clean up files needed for the current pipeline. Moreover, if files are cleaned up it should somehow mark the artifact as useless (at least as far as staging is concerned).
Relevant logs and/or screenshots
[--:--:--] START core/gnome-initial-setup.bst: Staging dependencies
... (a lot of SUCCESSful staging operations)
[00:00:05] SUCCESS core/gnome-initial-setup.bst: Staging dependencies
[00:00:07] FAILURE core/gnome-initial-setup.bst: Could not find file at /home/abderrahim/.cache/buildstream/cas/objects/75/eb0f6888c3107427fdb49c6b2441e0ce365c5f9337efe88efb757078e12c06
Other relevant information
- BuildStream version affected: 0591b0c8