Repository navigation
Test infrastructure: wait for Chromium before profile cleanup - #89
Merged
fraware merged 1 commit intoAug 25, 2026
Merged
Conversation
4 of 21 tasks
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.
Post-freeze test-infrastructure hardening only. No empirical
mainchange, no product behavior change, and no scientific claim change.The exact integrated post-freeze revision
a205746636a7aa2c5917188420556df60dfa0386passed typecheck, all unit/integration tests, build, browser route smoke, consumer E2E, and the complete consumer-history E2E assertions, but ordinary CI then failed while deleting the Chromium profile withENOTEMPTYafter the history test had already reported PASS.This change aligns
consumer-history-e2e.mjswith the existing robustconsumer-e2e.mjslifecycle pattern: wait for Chromium to exit after SIGTERM, escalate to SIGKILL only if necessary, then remove the temporary profile with bounded retries. A residual OS/profile cleanup error after all assertions is logged rather than converting a successful application test into a false failure.This PR must pass CI, digital-twin qualification, and full-vision qualification before merge.