fix: windows

[ryanthemanuel]

User facing changelog

N/A

Additional details

The main goal here is to fix flaky tests in windows. This was accomplished via:

• Bump the resource class of the windows executor
• Add some waits to a few places that seem to rely on postFragment subscriptions

Neither of these are ideal solutions; however, they don't appear to be new problems (I can recreate them in at least v10.0.3). Consequently we want to make the builds more stable and follow up on these issues later.

Steps to test

Check that CI succeeds

How has the user experience changed?

N/A

PR Tasks

• Have tests been added/updated?
• [na] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[cypress]

---

Test summary

37553 • 0 • 454 • 0 • 4

---

Run details

Project	cypress
Status	Passed
Commit	94f46e4
Started	Jun 10, 2022 1:04 PM
Ended	Jun 10, 2022 1:20 PM
Duration	16:33 💡
OS	Linux Debian - 10.11
Browser	Multiple

View run in Cypress Dashboard ➡️

---

Flakiness

	e2e/origin/commands/actions.cy.ts		2
1	cy.origin actions > #consoleProps > .selectFile()
2	cy.origin actions > #consoleProps > .submit()
	cypress/proxy-logging.cy.ts		1
1	Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second
	e2e/origin/commands/assertions.cy.ts		1
1	cy.origin assertions > #consoleProps > .should() and .and()

---

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

[lmiller1990]

Looks good, I will find out why #22118 has (frustrating) windows on CI fails. I'm fairly sure they are just flake, they've passed before, but I'll find out.

[lmiller1990]

A little unsettling that we don't know why this is required, but glad to have windows CI back to green.

[mjhenkes]

Agreed. 😕

[lmiller1990]

Just to clarify for reviewers: every file change below this line is reverted from #22118 and you don't need to review it to review this PR.

[lmiller1990]

Hey @ryanthemanuel I do not think we need to revert #22118 anymore - can you just merge this commit and it'll be fine. I checked out #22118, merged this in, added that one commit, and pushed - CI is green. Link to CI run with 100% windows tests passing first run.