-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
build: unrecognized build failure on gotip-linux-amd64-newinliner that was actually due to a core file being left behind #65977
Comments
Found new dashboard test flakes for:
2024-02-26 20:46 gotip-linux-amd64-newinliner go@4760b333 [build] (log)
|
The actual failure in this log is:
(attn @golang/runtime) @cherrymui, the |
I think it looks odd because watchflakes talks to the result database directly, and there's currently no place to put package-level failures. When this happens, I bet watchflakes probably just tries to link to the output directly instead of picking out the package-level failure directly. Seems like there are two things we can do here. One thing is that we can modify The other thing that can be done is to have watchflakes parse the output of the log and truncate it. This might actually be harder right now because of the text emitted by the wrapper commands. |
The snippet is the failed test output (if any), if there is no individual test failure (like a build failure), then the log of the failed step, if still empty, the log of the build. It currently extracts the first and last a few lines, and middle a few lines if there is a "useful" information. For "useful" it currently looks for "panic:", "--- FAIL:", etc. but does not look for just "FAIL". I'll make it include "FAIL" as well, then it will print the middle lines including
|
Based on issue #69457, the watchflakes change described in #65977 (comment) above is done. It sounds like there's nothing more to do here, and we can use that issue to track core files sometimes being left behind. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: