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
While investigating the high rate of flakiness in TestOrphanedFiles, I
found two problems:
- The change to use Await(...) rather than AfterChange(..), which was
intended to *avoid* flakes due to asynchronous log messages, actually
increased flakiness. After that change, the test can sometimes proceed
to make additional edits before change processing completes, so that
the load succeeds but the snapshot is cloned before the resulting
state can be written (sigh...).
- If the load succeeds, we should proceed to update state even if the
context is cancelled. Writing the state is not expensive.
Fixesgolang/go#61521
Change-Id: I4e70526a0108013c66d378da966289a7c2f5dbe2
Reviewed-on: https://go-review.googlesource.com/c/tools/+/518975
TryBot-Result: Gopher Robot <[email protected]>
Run-TryBot: Robert Findley <[email protected]>
Reviewed-by: Alan Donovan <[email protected]>
gopls-CI: kokoro <[email protected]>
0 commit comments