Thanks, Manuel! After changing --disk_cache to another location the error went away.Regards,HaiXinOn Fri, May 10, 2024 at 1:45 PM Manuel <naranjo...@gmail.com> wrote:. cache/bazel is where Bazel will expand all the internals, better to go with cache/bazel-disk or something.The issue you're hitting is deep in the guts, it happens when you cache the entire cache dir, Bazel gets confused by the mtime of those files which doesn't match expectations
The error is thrown from a file validation check that Bazel does to ensure no files have been tampered with.
https://github.com/bazelbuild/bazel/blob/1d20ea76113e49f7fb607ef92231f3665797b8e6/src/main/cpp/util/file_posix.cc#L458
Someone submitted a hack for Scala that touches the files:
https://github.com/bazelbuild/bazel/commit/cb2e03322be3f34b28df22ea17fe05e16fd2466d
It is not clear how to get around this as the original issue and idea is 5 years old. For now, since the fix is simple and there is little downside risk, we can go ahead with this and deal with the core issue at another time.
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/f7b8d9a7-6751-419a-ada5-a38d42667fdan%40googlegroups.com.
. cache/bazel is where Bazel will expand all the internals, better to go with cache/bazel-disk or something.The issue you're hitting is deep in the guts, it happens when you cache the entire cache dir, Bazel gets confused by the mtime of those files which doesn't match expectations
El vie, 10 may 2024, 22:05, HaiXin Tie <thx...@gmail.com> escribió:~/.cache/bazel is used as the disk-cache, with the following line in .bazelrc:build --disk_cache=~/.cache/bazelRegards,HaiXin
~/.cache/bazel is used as the disk-cache, with the following line in .bazelrc:build --disk_cache=~/.cache/bazelRegards,HaiXin
On Fri, May 10, 2024 at 11:16 AM Manuel <naranjo...@gmail.com> wrote: