Since these failures were all clustered around a few CLs on 2022-08-08, it's not clear to me whether this was a regression that has been fixed or a flaky test that happened to correlate in time due to some external factor.
@FiloSottile, @golang/security: are you aware of any changes that would explain this apparent regression and/or its fix?
The text was updated successfully, but these errors were encountered:
Nice, thank you for the reference! That does seem to explain these failures.
I think I spotted the bug, and left a comment about it on https://go.dev/cl/405674. If you'd like to retry that change, you're welcome to mail to to me — I can also suggest some unit-tests that might expose that race. 🙂