You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a known issue, without a good work-around.
Currently, if I want to clear the cache, I run sudo ~/.cache/bazel/, but this is a terrible idea.
More to the point, originally, we've designed the cache to work in tandem with bazel, so that if I do dazel build and then right away bazel build, it'll be the same exact cache. Back when that feature worked, the workaround would be to run bazel clean. This feature broke long ago (I think somewhere around bazel 0.3.0 or even earlier).
The ticket then should be one of the following:
Either fix the cache to work with bazel (although, i'm not hopeful it'll hold for very long again, due to changes in bazel),
or redesign the cache to work completely separate from bazel, and thus make it way simpler.
ERROR: /home/nathan/.cache/bazel/_bazel_nathan/9a314670874df4bb3656ae2f987d35fc/action_cache (Device or resource busy)
I believe this fails because action_cache is a volume mount by default in dazel. Is this a known issue with a proper workaround?
The text was updated successfully, but these errors were encountered: