Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
It's not obvious to me what test or what build of a test is causing the failure (just must be some test after sync/atomic). But I tried reproducing the failure by running the following command (which executes a sequence of tests around the point where things failed) repeatedly via gomote to darwin-arm64-corellium:
I couldn't reproduce -- never got any failures in 50 runs. So, I think we'll probably just have to wait & see if there are any other failures from builders.