-
Notifications
You must be signed in to change notification settings - Fork 2.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: upgrade the windows orb #1356
Conversation
520bbaa
to
24c4be9
Compare
24c4be9
to
5e647b3
Compare
Thanks very much for making these changes!
|
Of course! I don't think fixing the timeout issues will be straight forward, but at least we can get on Node 16 here 😅 |
@MikeMcC399 I have a feeling I am not going to get a passing windows run, am I? 😅 |
I'm seeing the error message:
So to get around this, the timeout on Cypress Cloud would need to be increased. Windows takes a long time to set up. Retriggering CircleCI would probably also not work due the timeout. To retest you would probably better push a new commit. |
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## develop #1356 +/- ##
========================================
Coverage 89.68% 89.68%
========================================
Files 19 19
Lines 737 737
Branches 35 35
========================================
Hits 661 661
Misses 76 76 ☔ View full report in Codecov by Sentry. |
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.
Congratulations 🙂 ! Apart from the flaky test (see #1332) it's all working.
So I think this PR can be merged. The other problems are all registered with their own dedicated issues, so these can be followed up separately.
Upgrades the Circle orb from 4.x.x to 5.x.x and sets up Node 16.16.0 via nvm to be consistent with our other jobs inside circle.