Repository navigation
RAL-179: a Chrome segfault at start gets the one stated retry; a teardown crash is said - #266
Merged
Merged
Conversation
…down crash is said From the lamplighter's third crash on Murph (SIGSEGV through zypak's bus call, at teardown, seen only in coredumpctl). A 139/SIGSEGV at start is retried once like RAL-160's abort, and a second fails. A crash as Chrome is closed, and each Chrome core coredumpctl lists since the run began, is said on standard error and carried to the test's; observed only, the result stands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 14, 2026
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.
RAL-179, assigned by the watchman, from the lamplighter's third Chrome crash on Murph (2026-11-14 05:29:59, SIGSEGV in /app/extra/chrome via zypak→libsystemd, during ci-local's check of 90de3d3, which passed and logged nothing of it).
retried_after_abort. A second crash fails ("Chrome crashed at start twice"), so a Chrome that crashes every time still fails. The retry stays one.tests/web.rscarries those lines to the test's own stderr, so ci-local's log has them even on a pass.RALLY_BROWSER_COREDUMPCTL).🤖 Generated with Claude Code