-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chromium Site Isolation - Legacy Binding Test failure #3867
Comments
We should add a legacy binding test to the |
amaitland
added a commit
that referenced
this issue
Nov 19, 2021
… when run via AppVeyor Is failing all the time now. Issue #3867
Tests are failing consistently now when run via Appveyor. Test will be skipped when run under |
amaitland
added a commit
that referenced
this issue
Apr 6, 2022
amaitland
added a commit
that referenced
this issue
May 31, 2022
amaitland
added a commit
that referenced
this issue
Aug 8, 2022
amaitland
added a commit
that referenced
this issue
Aug 9, 2022
amaitland
added a commit
that referenced
this issue
Sep 8, 2022
- Now that https://bitbucket.org/chromiumembedded/cef/issues/3260/support-reconnect-of-mojo-frame-channel has been resovled see if the tests will run on appveyor reliable - Use a new RequestContext to isolate the unreliable test cases. Issue #3867
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit 221185b enabled site isolation by default for
master
Tests are passing with the exception of IntegrationTestFacts.LoadLegacyJavaScriptBindingQunitTestsSuccessfulCompletion. Same test passes when I run it through
Visual Studio Test Explorer
. A new issue should be created and debugged at some point to determine the cause and evaluate if it's fixable or ifupstream
changes are required.Originally posted by @amaitland in #2967 (comment)
The text was updated successfully, but these errors were encountered: