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

test: fix flaky browser-multiple.test.ts #7510

Merged
merged 7 commits into from
Feb 21, 2025

Conversation

hi-ogawa
Copy link
Contributor

@hi-ogawa hi-ogawa commented Feb 18, 2025

Description

This one keeps failing, so I added a quick workaround. Fixed by making test/cli sequential with singleFork

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

Copy link

netlify bot commented Feb 18, 2025

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 3567678
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/67b80842ca95a90008cb1325
😎 Deploy Preview https://deploy-preview-7510--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@hi-ogawa hi-ogawa marked this pull request as ready for review February 18, 2025 09:12
Copy link
Member

@sheremet-va sheremet-va left a comment

Choose a reason for hiding this comment

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

I don't think this fixes the issue, there must be something more to this

@@ -11,6 +11,9 @@ it('automatically assigns the port', async () => {
onTestFinished(() => spy.mockRestore())
let ctx: Vitest
let urls: (string | undefined)[] = []
// override default port since it can conflicts with
// other browser mode tests in test/cli suite
Copy link
Member

Choose a reason for hiding this comment

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

test/cli runs sequentially, they should not affect each other

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think it's sequential. I noticed config has thread options

poolOptions: {
threads: {
singleThread: true,
},
},

Is this meant to be singleFork? or fileParallelism: false is fine?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, it's supposed to make tests run sequentially

@hi-ogawa hi-ogawa requested a review from sheremet-va February 21, 2025 05:14
@sheremet-va sheremet-va merged commit 28ad51b into vitest-dev:main Feb 21, 2025
13 checks passed
@hi-ogawa hi-ogawa deleted the test-flaky-browser-mutliple branch February 21, 2025 07:41
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