-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
feat(ci): run integration tests on windows #6279
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
7 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
@@ -80,7 +80,7 @@ Validate that we got a full task summary for the failed task with an error in .e | |||
"execution": { | |||
"startTime": [0-9]+, (re) | |||
"endTime": [0-9]+, (re) | |||
"error": "command .* npm run maybefails exited \(1\)", (re) | |||
"error": "command (.*)npm run maybefails exited \(1\)", (re) |
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.
This came from Rust tests, I thiink it's unrelated to this PR, but I was cross cehcking that test suite to make sure anything didn't break
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.
I'd like to see the Windows integration tests get to running the integration test. Currently they're failing on building the binary.
I also don't love distributing our own compiled version of echo $@
. I can accept that we might need an executable due to lack of Windows shebang support, but I think at minimum we should include the source in repo. In the ideal world we'd just add the compilation step as a task-dependency to the integration tests and avoid checking in binaries, but if that's not easily doable I think it's also okay to have a script that refreshes checked in binaries.
turborepo-tests/integration/tests/task-dependencies/topological.t
Outdated
Show resolved
Hide resolved
- Add turbo.exe stub source into this repo - Run it as a task dependency of integration tests - Place the turbo.exe in the appropriate folders in the fixtures
It builds and runs the tests for the Go codepath, which is where I started a few weeks ago now. I've disabled the Rust codepath, which is failing to build. I'd like to debug that separately so we can get something merged (it might take me some time to look into this.
Done, see #6508 or e010acb for details.
For what it's worth I don't think this is the problem. Executing these |
Linux Benchmark for 5267d8e
Click to view full benchmark
|
Linux Benchmark for 9ea5945Click to view benchmark
|
Linux Benchmark for bc8911fClick to view benchmark
|
Linux Benchmark for b98b9aeClick to view benchmark
|
Linux Benchmark for 2cc6b6eClick to view benchmark
|
The |
This PR enables starts running our integration tests on Windows and fixes some of the
issues that come out of that. Mostly the issues are around finding binaries with
.exe
extension (the test runner and turbo itself), file path separators, and line endings.
This PR adds a new Github Action "job" for both the Go and Rust variants, because
there are still a few remaining tests that are not passing that will need a little more
investigation. Once this diff is merged, we can individually look at each test (e.g. #6477)
Closes TURBO-1533
Some Prysk references
environb
on some platforms prysk/prysk#183