Skip to content
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

chore(ci) test on Node.js v22 and not v16 #3052

Merged
merged 1 commit into from
Jul 23, 2024

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Jul 22, 2024

Checklist
  • npm install && npm run lint && npm test passes
  • tests are included
  • documentation is changed or added
  • commit message follows commit guidelines
Description of change

cross-env NODE_GYP_NULL_LOGGER=true mocha --timeout 15000 test/test-download.js test/test-*

sh: cross-env: command not found

include: # `npm test` is running Windows find-visualstudio tests on an M1 Mac!!!
- os: macos-14
node: [18.x, 20.x, 22.x]
include: # `npm test` runs Windows find-visualstudio tests on an Intel Mac!!!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think M1 Mac is more reasonable since intel not produced anymore

Copy link
Contributor Author

@cclauss cclauss Jul 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarification: On GitHub Actions macos-latest is now macos-14 on M1 while macos-13 is legacy Intel.

Before we were mostly testing on Intel and only one test run on M1. This change reverses that. Intel is still used broadly even if it is no longer being sold.

More important is why the Node.js v22 tests are failing.

@cclauss cclauss merged commit e6f4ede into main Jul 23, 2024
37 checks passed
@cclauss cclauss deleted the chore(ci)-test-on-Node.js-v22-and-not-v16 branch July 23, 2024 04:50
This was referenced Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants