Repository navigation
Retain optional signed-out browser failure evidence - #20
Merged
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
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 browser test can fail in Linux CI without leaving the trace needed to diagnose it. The reusable Test workflow now accepts optional signed-out output paths and retains them for three days when the Browser tests step fails. Callers that leave the input empty keep their current behavior.
Fulldev will opt in only its Chromium, Firefox and WebKit signed-out directories. Signed-in output remains excluded, and failures still fail the job.
Validation: actionlint passed; all 39 policy tests passed. Independent review approved the shared workflow and verified that Fulldev’s selected folders exclude signed-in and test-access output. Fulldev will pin the merged shared revision before opting in.