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

Different test coverage reports on different computers #3805

Closed
6 tasks done
pkolt opened this issue Jul 24, 2023 · 2 comments
Closed
6 tasks done

Different test coverage reports on different computers #3805

pkolt opened this issue Jul 24, 2023 · 2 comments
Labels
feat: coverage Issues and PRs related to the coverage feature needs reproduction

Comments

@pkolt
Copy link

pkolt commented Jul 24, 2023

Describe the bug

Hi! It seems to me that this bug appeared in one of the new versions. Because before the update to 0.33 everything worked without errors. Different computers produce different test coverage results.

Here the problem is not in CircleCI, I tried to run coverage on another Linux computer, the result was also different from coverage on a Macbook.

Reproduction

TZ=UTC vitest --bail=1 --coverage.enabled --coverage.reporter='text-summary' --coverage.reporter='html' --reporter=junit --outputFile=./reports/junit/test-results.xml

System Info

System:
    OS: macOS 13.4.1
    CPU: (10) arm64 Apple M2 Pro
    Memory: 392.42 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    npm: 9.6.6 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 115.0.5790.102
    Safari: 16.5.2
    Safari Technology Preview: 17.0

Used Package Manager

npm

Validations

@github-actions
Copy link

Hello @pkolt. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

@AriPerkkio
Copy link
Member

The 0.33.0 release shouldn't change anything coverage related. And it looks like you are using @vitest/coverage-istanbul which hasn't had any big changes recently.

Without being able to reproduce this issue I have no idea what could cause it.

@AriPerkkio AriPerkkio added feat: coverage Issues and PRs related to the coverage feature and removed pending triage labels Jul 25, 2023
@pkolt pkolt closed this as completed Jul 25, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Aug 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feat: coverage Issues and PRs related to the coverage feature needs reproduction
Projects
None yet
Development

No branches or pull requests

2 participants