-
-
Notifications
You must be signed in to change notification settings - Fork 643
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
missing digest on main
and 2.13.x
branch
#15995
Comments
cc @stuhood |
Another example (but on
https://github.com/pantsbuild/pants/runs/7116113010?check_suite_focus=true#step:9:279 |
Same build failed again but only with local store this time:
https://github.com/pantsbuild/pants/runs/7116545174?check_suite_focus=true#step:9:242 |
main
main
and 2.13.x
branch
Would cherry-picking #15979 help? |
No, it won't: this is an async method failing rather than a sync method failing. Thanks for the cherry-pick though anyway! I'll need to re-audit whether the |
This is apparently because that build failed to authenticate to Toolchain:
...and so remote caching was disabled. How it then encountered an unrecoverable |
#16008 should slightly adjust the output for this error. I'll be on the lookout for additional cases, but please report them if you see them. |
Noting these last 3 above were all from the same PR / were re-runs. They all failed on the same missing digest. The 4th run succeeded apparently only because of a failure acquiring BuildSense auth. |
If this is causing folks enough trouble, we can re-enable eager_fetch until it is resolved: Lines 71 to 72 in 8efc396
|
I'm prepping that PR presently - red main should not be tolerated / this is in fact causing pain. |
Band-aids pantsbuild#15995 in CI. [ci skip-rust]
A race condition was possible in backtracking where if a `Node` which produced a particular `Digest` had already been invalidated by one consumer, a second consumer would fail to find a source for the `Digest`, and would report "Could not identify a process to backtrack to". Fixes #15995.
A race condition was possible in backtracking where if a `Node` which produced a particular `Digest` had already been invalidated by one consumer, a second consumer would fail to find a source for the `Digest`, and would report "Could not identify a process to backtrack to". Fixes pantsbuild#15995. [ci skip-build-wheels]
A race condition was possible in backtracking where if a `Node` which produced a particular `Digest` had already been invalidated by one consumer, a second consumer would fail to find a source for the `Digest`, and would report "Could not identify a process to backtrack to". Fixes #15995. [ci skip-build-wheels]
Observed a missing digest on
main
even with backtracking changes in place:https://github.com/pantsbuild/pants/runs/7113601869?check_suite_focus=true#step:13:424
The text was updated successfully, but these errors were encountered: