Repository navigation
Scope rearm assertions to the receipt status region - #704
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
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.
The genuine opt-in Chromium tests stopped at both new rearm assertions because the external reference contains two descendant status elements. Select the direct-child receipt status, following the existing reconnect assertion, and retain the exact rearm sentence plus all generation, unknown-receipt and fresh-correlation assertions.
Validation: the authentic native run38167767850/a1 report proves both strict-mode violations; bounded original archive/log diagnosis and source diff checks passed. The sibling locator sweep has no remaining broad status locator in these reference tests. Genuine opt-in qualification remains pending: the maintained candidate runner must pass all eight selected cases in each of Chromium, Firefox and WebKit with zero skips/flaky/unexpected results. Ordinary hosted browser success does not establish that opt-in qualification or native Orca journey acceptance.