-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cleanup(js): fix test cases on windows #27300
cleanup(js): fix test cases on windows #27300
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 6a98430. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
@robertIsaac thanks for sending these fixes! Could you please rebase the PR? I believe some of the fixes here might have already landed on |
fb462fa
to
d3fa62f
Compare
@leosvelperez done |
packages/js/src/generators/release-version/utils/resolve-version-spec.spec.ts
Outdated
Show resolved
Hide resolved
packages/js/src/generators/release-version/utils/resolve-version-spec.spec.ts
Outdated
Show resolved
Hide resolved
packages/js/src/generators/release-version/utils/resolve-version-spec.spec.ts
Outdated
Show resolved
Hide resolved
5f0ce3a
to
91ad3f0
Compare
91ad3f0
to
6a98430
Compare
and @leosvelperez
and if this file is enabled, almost all of the tests fail with it being ignored (using xdescribe)
with it being active
|
I'm unsure about that one. Let's merge this and I'll try to set some time next week to check it. |
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.
Thanks for the contribution!
## Current Behavior running `nx test js` fail on windows ## Expected Behavior running `nx test js` succeed ## side notes 1. I was skipping `packages/js/src/plugins/typescript/plugin.spec.ts` because it makes all tests fail, and even in wsl it's very flaky, it fail 90% of the times, but I couldn't figure out why I think it's worth looking at from someone with more experience with the repo 2. for some of the cases that I fixed I'm not sure if I should change the code to always return `/` or should change the test to adapt `/` in linux and `\` in windows, so please if I mistaken one of them let me know and I will do it the other way around but I believe it should be fine since in windows `foo/bar` does work as a path still (cherry picked from commit 69c989e)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
running
nx test js
fail on windowsExpected Behavior
running
nx test js
succeedside notes
packages/js/src/plugins/typescript/plugin.spec.ts
because it makes all tests fail, and even in wsl it's very flaky, it fail 90% of the times, but I couldn't figure out whyI think it's worth looking at from someone with more experience with the repo
/
or should change the test to adapt/
in linux and\
in windows, so please if I mistaken one of them let me know and I will do it the other way around but I believe it should be fine since in windowsfoo/bar
does work as a path still