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
This builder config might be new. I forget whether we ever tested nacl against subrepos before. Maybe we shouldn't? Especially if we plan to delete nacl anyway (#30439).
As for gomote, perhaps its environment is slightly wrong in its config. Can you test other subrepo nacl stuff via gomote successfully?
This builder config might be new. I forget whether we ever tested nacl against subrepos before. Maybe
we shouldn't? Especially if we plan to delete nacl anyway (#30439).
I assume it got activated by https://golang.org/cl/166218? In any case it's then probably not worth bothering about x/sys/cpu failing on nacl if it's going to be deleted.
As for gomote, perhaps its environment is slightly wrong in its config. Can you test other subrepo nacl stuff via gomote successfully?
I didn't try any other subrepos as I just wanted to quickly see whether I can get some additional info on the failing test.
The
x/sys/cpu
tests fail on the nacl-386 and nacl-amd64p32 builders:https://build.golang.org/log/cc4f59f7b4f276707e7bcdde980e0329520f99e7
https://build.golang.org/log/a0e3434d13a77b080e3f6d2d176d96bd368dc1ef
when executing via gomote I get
/cc @bradfitz @ianlancetaylor
The text was updated successfully, but these errors were encountered: