Repository navigation
Conversation
A run's own output goes to <test>-<alloc>-out.txt and that file does not reach a CI log, so a test that dies says nothing beyond its name: in the failing rocksdb jobs the log shows the run starting and the next test starting 0.1 s later, with no error text anywhere. Report the exit status - naming the signal when the run was killed by one - and the tail of the output file, on stderr so buildkit records it. Name a signal only when the shell knows that number, and always keep the status: a program can exit() above 128 as well, and guarder's fatal errors do (exit 255), which an unconditional 128 offset would report as a nonexistent "signal 127".
derSteFfi
force-pushed
the
bench_fail_details
branch
from
November 12, 2026 16:29
f718480 to
97ce865
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A run's own output goes to
<test>-<alloc>-out.txtand that file does not reach a CI log, so a test that dies says nothing beyond its name: in the failing jobs for #287 the log shows the run starting and the next test starting 0.1 s later, with no error text anywhere. Report the exit status - naming the signal when the run was killed by one - and the tail of the output file, onstderrso buildkit records it.