<@U06A03HV1> I think this change is flaky: <https:...
# development
b
@witty-crayon-22786 I think this change is flaky: https://github.com/pantsbuild/pants/runs/7168283470?check_suite_focus=true
Copy code
Exception: Could not identify a process to backtrack to for: Missing digest: Was not present in either the local or remote store: Digest { hash: Fingerprint<c1bb310e89f1fc9a949e27af32856cef51b8c34a8886d1aa2fd9927545e142e8>, size_bytes: 3509 }
e
b
Yeah I keep getting it OVER and OVER. Woof 😔
According to our flakiness policy, the change should technically be reverted. It's hurting maintainers, and likely outside contributors (whose time and success are extremely valuable)
e
I did not look in detail, but the ticket seems to imply this is not simple. There is more than one commit involved and cherry-picks already to branches.
b
Are we not worried about end-users?
e
We are all the we here. If you'd like to take this up, please do. You're right about the policy and this is not a good situation. That said, its a US holiday weekend, the fix in either direction will take care and effort, and the original players are offline.
Perhaps the simplest remedy is to disable the remote cache in CI. IIUC that fixes this. As I noted on the ticket anyhow a failure to log in to the remote cache is what unstuck my most recent case.
FWIW its easy to examine outside user pain and that == 0 right now: https://github.com/pantsbuild/pants/actions It's me, you, Benjy and configloyd - but he has only green actions.
b
I was being sincere. It actually seems like end users aren't hurting, so fixing might just be the easiest path forward
e
Oh, I don't doubt your sincerity. Just a nudge to check a fear instead of resting in FUD. I agree, I think it's best to wait on this one until Tuesday am or at most alter CI to not use the cache.
w
this is a non-default behavior: can set
eager_fetch=true
to disable it https://github.com/pantsbuild/pants/blob/8efc3961a599e1f5fd147db171a2ace617274db3/pants.toml#L71-L72
👀 1
e