-
Notifications
You must be signed in to change notification settings - Fork 18k
context: TestDeadline is flaky #13956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@bradfitz – is there a way to grep the builder's outputs? As far as I can see this is only flaky in win 386, but that's based on random sampling failures. I can't repro it locally in linux x64 yet. Taking a look at the code now, but I'm not too familiar with it so might take a while. |
@aclements has such powers. See x/build/cmd/fetchlogs. Austin also has more tools (not checked in?). |
Fetchlogs doesn't grab the subrepos and findflakes doesn't know how to deal with them either. :/ |
That's (at least partially) #35515. Fortunately, 2020-02-21T20:28:45-675a2e7/solaris-amd64-oraclerel |
Change https://golang.org/cl/223019 mentions this issue: |
http://build.golang.org/log/fb80b1a87de755770f8959badca24f07e10689ab
/cc @okdave @Sajmani or whoever owns this
The text was updated successfully, but these errors were encountered: