4 ms·
I assumed they meant an error of improperly using cached results. I am sure bazel has its flaws but it assiduously avoids that.
by jeffbee 2y ago
I assumed they meant an error of improperly using cached results. I am sure bazel has its flaws but it assiduously avoids that.
- __float 2y agoYes, unless you're using persistent workers. Then you may very well run into the same issues they mention.
- sunshowers 2y agoI did mean improperly using cached results. It's merely the hardest problem in computer science :) The sibling suggests this may still be an issue. I'm not surprised—cache invalidation is very difficult to solve, and conservative approximations like tearing down the whole process each time tend to be quite effective.