ci: recognize glibc heap-corruption aborts in ci-annotate-errors - #38702
Open
ggevay wants to merge 1 commit into
Open
ci: recognize glibc heap-corruption aborts in ci-annotate-errors#38702ggevay wants to merge 1 commit into
ggevay wants to merge 1 commit into
Conversation
A process that dies of a glibc heap-consistency abort (malloc(): ..., free(): ..., double free or corruption, stack smashing) leaves only that one stderr line behind. ERROR_RE did not match it, so the job annotated as "failed, but no error in logs found", no known-issue regexp could attach, and the failure history could not record it. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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
1 participant
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.
Motivation
Nightly 18265's
testdrive with FoundationDB 1died withmalloc(): unsorted double linked list corruptedon testdrive's stderr (PER-82).ERROR_REinci_annotate_errors.pyhas no alternative for glibc's heap-consistency messages, so the job was annotated as "failed, but no error in logs found", noci-regexpcould attach to it, and the failure history has no record of the signature. Part of QAR-158.Description
Add the glibc heap-abort messages to
ERROR_RE:malloc()/free()/realloc()/munmap_chunk():,double free or corruption,corrupted size vs. prev_size,corrupted double-linked list, andstack smashing detected. Addstest_glibc_heap_abort_is_an_errortoci_annotate_errors_test.py; it fails without the pattern change.Verification
The new test and the existing annotator tests pass; black and ruff are clean on both files.
🤖 Generated with Claude Code