-
Notifications
You must be signed in to change notification settings - Fork 18k
internal/trace/v2: TestTraceStressStartStop failures #65559
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
Found new dashboard test flakes for:
2024-01-24 21:35 openbsd-386-72 go@333ecd4b internal/trace/v2.TestTraceStressStartStop (log)
|
Found new dashboard test flakes for:
2024-02-23 00:19 openbsd-386-72 go@d9be6097 internal/trace/v2.TestTraceStressStartStop (log)
|
Found new dashboard test flakes for:
2024-02-28 16:44 windows-arm64-11 go@db8c6c8c internal/trace/v2.TestTraceStressStartStop (log)
|
Found new dashboard test flakes for:
2024-03-01 08:06 windows-arm64-11 go@b5a64ba6 internal/trace/v2.TestTraceStressStartStop (log)
|
The fix for #65318 landed. Closing this issue as well. |
Found new dashboard test flakes for:
2024-03-23 04:07 openbsd-386-72 go@83a6c13e internal/trace/v2.TestTraceStressStartStop (log)
|
We lost the trace here because of a mistake. I sent a CL to rectify the mistake. Unfortunately there's not much we can do here without being able to inspect the trace. These failures seem incredibly rare at this point. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: