-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime/trace: OOM in TestTraceStressStartStop on openbsd/386 #64322
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
I'm a bit baffled as to why this is happening now. That test only ever runs the old execution tracer. Coincidentally, I recently landed a CL that switches to the new tracer, so this test should be skipped now. (There's an equivalent test in internal/trace/v2, but it's already been running on the builders and hasn't had an OOM issue on OpenBSD yet.) |
Note: a bunch of these failures also showed up at #53576. |
Maybe some other test is running in parallel, or expanding the runtime's memory footprint in a way that leaks some additional pages? |
Found new dashboard test flakes for:
2023-11-16 19:26 openbsd-386-72 go@d573a8a8 runtime/trace.TestTraceCPUProfile (log)
2023-11-20 15:56 openbsd-386-72 go@1d187fd0 runtime/trace (log)
2023-11-21 16:29 openbsd-386-72 go@78d037b0 runtime/trace (log)
2023-11-21 17:59 openbsd-386-72 go@070139a1 runtime/trace (log)
2023-11-21 20:34 openbsd-386-72 go@00715d08 runtime/trace (log)
2023-11-21 21:27 openbsd-386-72 go@351d8520 runtime/trace (log)
2023-11-21 21:27 openbsd-386-72 go@48a6362d runtime/trace (log)
2023-11-21 21:29 openbsd-386-72 go@90ba4452 runtime/trace (log)
|
This has probably stopped happening since the new tracer was turned on by default, since this test isn't run anymore. In that sense it's fixed, but if for whatever reason the new tracer gets rolled back, watchflakes will probably reopen this if I close it. So, I'm going to optimistically close it but leave it open so I remember to resolve it if that happens. I am not particularly concerned that this is going to be anything more than a test issue. |
Found new dashboard test flakes for:
2024-02-02 16:26 openbsd-386-72 go@2fdad8af runtime/trace.TestTraceCPUProfile (log)
|
Optimistically closing again. |
Example: https://build.golang.org/log/0be8c98902db83cc7880a398efe8f7d6c9225606
(from #53576)
(attn @mknyszek; CC @golang/openbsd)
The text was updated successfully, but these errors were encountered: