Skip to content

test: execute one yarn after another#141

Merged
Skn0tt merged 4 commits intomicrosoft:mainfrom
Skn0tt:two-runs
Feb 19, 2025
Merged

test: execute one yarn after another#141
Skn0tt merged 4 commits intomicrosoft:mainfrom
Skn0tt:two-runs

Conversation

@Skn0tt
Copy link
Copy Markdown
Member

@Skn0tt Skn0tt commented Feb 17, 2025

Follow-up to #138. Because the implementation hard-codes which Yarn it calls, there's no to test both yarn versions in parallel. This somehow slipped the last PR.

This PR changes it so that we have two separate ones, and we change the global yarn version in between.

@Skn0tt Skn0tt self-assigned this Feb 17, 2025
Comment thread .github/workflows/ci.yml Outdated
- run: npm run build
- run: npx tsc --noEmit
- run: npm run test
- run: npm run test -- --project=npm --project=pnpm --project=yarn-classic
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe this is more future proof?

npm run test -- --grep-invert yarn-classic
npm run test -- --grep yarn-berry

AFAIK grep includes project name.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

implemented in 97aa4bd

@Skn0tt Skn0tt merged commit 2a7b5ef into microsoft:main Feb 19, 2025
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.

2 participants