- Notifications
You must be signed in to change notification settings - Fork489
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
haoqunjiang wants to merge1 commit intovuejs:mainChoose a base branch fromhaoqunjiang:ci-exclude-cypress-windows
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
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 andfound that it's always the same EPERM error on Windows.It has been reported to us before that EPERM errors are happening onWindows + 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` tagto Windows Server 2025, `start-server-and-test` will break completely onour CI.`start-server-and-test` and `ps-tree` are largely unmaintained, sowe need to move away from `start-server-and-test` in the near future andthen we can re-enable Windows + Cypress tests.
MemberAuthor
haoqunjiang commentedJul 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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… |
Sign up for freeto 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-test
repository but it is still not resolved.bahmutov/start-server-and-test#384Furthermore, Windows 11 24H2 and Windows Server 2025 have removed the
wmic
utility, which is used bystart-server-and-test
(via theps-tree
dependency). Once GitHub Actions upgrades thelatest
tag to Windows Server 2025,start-server-and-test
will break completely on our CI.start-server-and-test
andps-tree
are largely unmaintained, so we need to move away fromstart-server-and-test
in the near future and then we can re-enable Windows + Cypress tests.