-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chore: merge develop into 10.0-release #20531
chore: merge develop into 10.0-release #20531
Conversation
…essage (#20335) * fix cy.fixture regression - strip ansi colors out of fixture error message * empty commit to appease the semantic release gods * fix 2nd regression formatting when setting invalid config values - remove extra backtick * increase webpack dev server timeout values
* chore: fix assertions * fix ExpectType for config.baseUrl
Co-authored-by: cypress-bot[bot] <2f0651858c6e38e0+cypress-bot[bot]@users.noreply.github.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: cypress-bot[bot] <2f0651858c6e38e0+cypress-bot[bot]@users.noreply.github.com>
Co-authored-by: Emily Rohrbough <emilyrohrbough@users.noreply.github.com>
Co-authored-by: cypress-bot[bot] <2f0651858c6e38e0+cypress-bot[bot]@users.noreply.github.com>
* Setting response header for origin-agent-cluster for runner, iframes, and proxied requests that have domain injection * Adding comments around header injection * Adding unit tests
…res images for uniqueness that represent the same state (#20463)
Co-authored-by: Renovate Bot <bot@renovateapp.com>
…warning message about chromeWebSecurity (#20512)
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
….com/cypress-io/cypress into marktnoonan/backmerge-develop-3-8-22
Easy one - changes seem fine, can you re-run CI to see if it's just flake? |
@lmiller1990 one of the CI failures was flake, the windows one was pre-existing on 10.0-release, but not usually run on PRs, so I'll make a bug ticket for what seems to be the cause of the flake. |
@lmiller1990 @flotwig I've fixed the failing windows tests in this branch now so we should be able to get the whole PR green. The fix is here: https://github.com/cypress-io/cypress/pull/20531/files#diff-6e2089ba2acfd61684acf48d4f7cf5419a1e1ac4c69c853af6a99630de5ca4c2R220 Talking with Lachlan this am we pinned it down to an unintended side effect of Zach if you approve I'm happy to merge w/o re-approval from Lachlan if he's offline, since the solution I added is small and in line with Lachlan's suggestion. |
@marktnoonan it seems weird to me that your change didn't require changing any tests, isn't this covered by some spec somewhere? |
@flotwig |
We had 14 files with merge conflicts this time around. Summary:
develop
was a higher version.circle.yml
conflict with branch names to test for in specific workflows, resolved by dropping old branches and adding this branch namedevelop
of the globalroot
variable fromspec_helper
that's been removed in10.0-release
The rest were straightforward conflicts where keeping both changes was fine, or it was obvious that, eg a deleted file in
10.0-release
that was edited indevelop
should stay deleted in10.0-release