Skip to content

Conversation

@nathanchance
Copy link
Member

See the individual changes for the full details.

Currently, we assume if we do not get a "complete" status back from the
build, the build is not completed. Recently however, there have been an
increase in internal TuxSuite infrastructure errors, which are not
obvious upon inspection.

If the build status is "error", print out the status message and exit
early, as we know that the build is done since it never started :)

Signed-off-by: Nathan Chancellor <[email protected]>
Internal errors (explanations of known problematic cases or an
unexpected result) should be printed more clearly so that triaging can
go quicker. Add a tag to print_red() and print_yellow() so that a
problem matcher can print them automatically, making it clear what
happened with the build.

Signed-off-by: Nathan Chancellor <[email protected]>
@nathanchance
Copy link
Member Author

I am going to merge this to help with triaging but if there are any post merge comments, I am happy to address them in a follow up.

@nathanchance nathanchance merged commit 5802870 into ClangBuiltLinux:main Jul 10, 2025
7 checks passed
@nathanchance nathanchance deleted the handle-internal-errors-better branch July 11, 2025 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant