Conversation
|
|
||
| it("should modify path correctly when on Windows", () => { | ||
| const env = ShellOps.getModifiedEnv("win32"); | ||
| if(process.platform === "win32") { |
There was a problem hiding this comment.
I've just wrapped the test cases with an if-else clause, so Windows tests run only on Windows, and Unix tests run on non-Windows environments.
This is because Bun CI fails on Windows, particularly for the Unix tests.
I suspect it's due to the Unix tests relying on a Unix-specific PATH, but they're being run on Windows.
FYI, the previous CI doesn't include Windows environment tests; adding regular tests that target Windows will cause failures.
https://github.com/eslint/eslint-release/actions/runs/18707118578/job/53347191545
| include: | ||
| - os: windows-latest | ||
| node: lts/* | ||
| - os: macOS-latest | ||
| node: lts/* |
There was a problem hiding this comment.
Added Windows and macOS tests for more robust testing.
6e656c1 to
cb1496c
Compare
…ci-create-ci-bun-yml
|
@aladdin-add If so, would only adding Windows and macOS tests to the existing Looking at the test code, the release tool appears to be intended for use across multiple platforms: eslint-release/tests/lib/shell-ops.test.js Lines 28 to 49 in cbc16bb (Also, there seem to be a few repositories that rely on this package?) |
|
There's no need to test this on bun as it's just a tool for the team's use. |
Prerequisites checklist
What is the purpose of this pull request?
In this PR, I've created
ci-bun.yml.This is part of the effort to centralize workflows mentioned in eslint/workflows#4.
The full workflow can be found here: https://github.com/eslint/workflows/blob/main/.github/workflows/ci-bun.yml
What changes did you make? (Give an overview)
In this PR, I've centralized
ci-bun.yml.Related Issues
Refs: eslint/workflows#15, eslint/workflows#4
Is there anything you'd like reviewers to focus on?
N/A