store rustwide command-error in build-table #3201
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
S-waiting-on-review
syphar
force-pushed
the
more-specific-build-errors
branch
from
ecf28a3 to
a0c9fab
Compare
syphar
force-pushed
the
more-specific-build-errors
branch
from
a0c9fab to
64b2aa0
Compare
syphar
changed the title
This was referenced Feb 11, 2026
GuillaumeGomez
approved these changes
Feb 11, 2026
Member
|
Thanks! |
github-actions
bot
added
S-waiting-on-deploy
syphar
removed
the
S-waiting-on-deploy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References #878
mainly: store the actual rustwide
CommandErrorkind in our build-result table. Through that we can directly see timeouts, OOM, ...At some point also have statistics.
I want to store it for a bit before I show it anywhere.