-
Notifications
You must be signed in to change notification settings - Fork 496
ci: skip Windows + Cypress temporarily #784
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
Merged
haoqunjiang
merged 1 commit into
vuejs:main
from
haoqunjiang:ci-exclude-cypress-windows
Jul 21, 2025
Merged
ci: skip Windows + Cypress temporarily #784
haoqunjiang
merged 1 commit into
vuejs:main
from
haoqunjiang:ci-exclude-cypress-windows
Jul 21, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I thought it was just random timeouts until I look into the logs and found that it's always the same EPERM error on Windows. It has been reported to us before that EPERM errors are happening on Windows + Cypress projects. The issue was later moved to the `start-server-and-test` repository but it is still not resolved. <bahmutov/start-server-and-test#384> Furthermore, Windows 11 24H2 and Windows Server 2025 have removed the `wmic` utility, which is used by `start-server-and-test` (via the `ps-tree` dependency). Once GitHub Actions upgrades the `latest` tag to Windows Server 2025, `start-server-and-test` will break completely on our CI. `start-server-and-test` and `ps-tree` are largely unmaintained, so we need to move away from `start-server-and-test` in the near future and then we can re-enable Windows + Cypress tests.
I'm glad that those time-consuming CI jobs have uncovered a real issue this time. 😂 I was considering skipping some of them just because of how slow they are before I found out this real bug...
btea
btea
approved these changes
Jul 21, 2025
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.
👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
I thought it was just random timeouts until I looked into the logs and found that it's always the same EPERM error on Windows.
It has been reported to us before that EPERM errors are happening on Windows + Cypress projects. The issue was later moved to the
start-server-and-testrepository but it is still not resolved. bahmutov/start-server-and-test#384Furthermore, Windows 11 24H2 and Windows Server 2025 have removed the
wmicutility, which is used bystart-server-and-test(via theps-treedependency). Once GitHub Actions upgrades thelatesttag to Windows Server 2025,start-server-and-testwill break completely on our CI.start-server-and-testandps-treeare largely unmaintained, so we need to move away fromstart-server-and-testin the near future and then we can re-enable Windows + Cypress tests.