Repository navigation
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.
An empty diff on top of the current
webuiHEAD. It exists to answer one question: does the macOS verification run fail inpackages/webui/test/integration/isolated-chromium-two-pages.test.tson this base too?The revert pull request failed that file twice on macOS, in two different ways: once as a DevTools
Input.dispatchMouseEventtimeout, once asbrowser_target_stale("the browser page was replaced"). Both failures live inpackages/webui/src/runtime/browser/isolated-chromium/, which the revert does not touch.This pull request changes nothing, so any failure here belongs to the base rather than to the revert.
Local runs of that file passed 3/3 and 12/12 on the revert branch.