-
Notifications
You must be signed in to change notification settings - Fork 13.8k
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
[cypress] Disable chromeWebSecurity globally #7853
[cypress] Disable chromeWebSecurity globally #7853
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
superset/assets/cypress.json
Outdated
@@ -5,6 +5,7 @@ | |||
"ignoreTestFiles": ["**/!(*.test.js)"], | |||
"projectId": "fbf96q", | |||
"defaultCommandTimeout": 10000, | |||
"chromeWebSecurity": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe sort in abc order? cc @john-bodley ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorted now.
a26b981
to
8995dd9
Compare
Codecov Report
@@ Coverage Diff @@
## master #7853 +/- ##
=======================================
Coverage 65.79% 65.79%
=======================================
Files 461 461
Lines 22097 22097
Branches 2423 2423
=======================================
Hits 14539 14539
Misses 7437 7437
Partials 121 121 Continue to review full report at Codecov.
|
CATEGORY
Choose one
SUMMARY
This PR is trying to resolve the same issue in #7552. In the old PR we disable chromeWebSecurity in single test file, but recently we saw a few build failure caused by this same root cause. So this PR will set disable chromeWebSecurity globally (and see if this can fix the flaky tests).
TEST PLAN
ci.
REVIEWERS
@mistercrunch