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

Running coverage tests litters output with debug messages #620

Closed
6 tasks done
robcaldecott opened this issue Jan 24, 2022 · 0 comments · Fixed by #622
Closed
6 tasks done

Running coverage tests litters output with debug messages #620

robcaldecott opened this issue Jan 24, 2022 · 0 comments · Fixed by #622

Comments

@robcaldecott
Copy link
Contributor

robcaldecott commented Jan 24, 2022

Describe the bug

When running tests with --coverage the output is littered with debug messages:

Debugger listening on ws://127.0.0.1:64213/bb456c21-2c1a-4576-b202-9a787e1731f6
For help, see: https://nodejs.org/en/docs/inspector

This is particularly obvious when CI=true, for example:

Debugger listening on ws://127.0.0.1:64213/bb456c21-2c1a-4576-b202-9a787e1731f6
For help, see: https://nodejs.org/en/docs/inspector
Debugger listening on ws://127.0.0.1:64214/6f2e4b07-6a7e-4c46-837e-0bfb9a96eae3
For help, see: https://nodejs.org/en/docs/inspector
 √ src/FilterProvider/FilterProvider.test.tsx > renders
 √ src/FilterProvider/FilterProvider.test.tsx > uses the correct initial values
 √ src/FilterProvider/FilterProvider.test.tsx > updates the filter
 √ src/FilterProvider/FilterProvider.test.tsx > throws an error when rendered outside of a FilterProvider
Debugger listening on ws://127.0.0.1:64215/18490320-b94e-4575-a340-d16569b3b23f
For help, see: https://nodejs.org/en/docs/inspector
Debugger listening on ws://127.0.0.1:64216/acce2902-5823-47cf-b308-010ba23ff1b3
For help, see: https://nodejs.org/en/docs/inspector
 √ src/Fallback/Fallback.test.tsx > renders
 √ src/Logo/Logo.test.tsx > renders
Debugger listening on ws://127.0.0.1:64217/eca3560b-c362-4475-86f8-f738714f7968
For help, see: https://nodejs.org/en/docs/inspector
 √ src/ErrorMessage/ErrorMessage.test.tsx > renders without an action
 √ src/ErrorMessage/ErrorMessage.test.tsx > renders with an action
 √ src/Details/AlertError.test.tsx > renders
Debugger listening on ws://127.0.0.1:64218/8750caac-56a3-4de7-8a36-8c4a7212842f
For help, see: https://nodejs.org/en/docs/inspector
Debugger listening on ws://127.0.0.1:64219/1e991790-5826-41ac-bf95-79c3d9c95671
For help, see: https://nodejs.org/en/docs/inspector
Debugger listening on ws://127.0.0.1:64220/ddc4727e-9e81-479f-bf07-c1525e62ee4c
For help, see: https://nodejs.org/en/docs/inspector
 √ src/AppHeader/AppHeader.test.tsx > renders
Debugger listening on ws://127.0.0.1:64225/71f89a98-2535-41f7-b0bd-27f5c0eea2b4
For help, see: https://nodejs.org/en/docs/inspector

<snip>

Reproduction

Clone this project:

https://github.com/robcaldecott/vite-kitchen-sink

npm install
CI=true npx vitest run --coverage

I think this was introduced via #584

System Info

System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 984.49 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v14.17.0/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 97.0.4692.99
    Firefox: 95.0.2
    Safari: 14.1.2
  npmPackages:
    @vitejs/plugin-react: ^1.1.3 => 1.1.4 
    vite: ^2.7.13 => 2.7.13 
    vitest: ^0.2.0 => 0.2.1

Used Package Manager

npm

Validations

@github-actions github-actions bot locked and limited conversation to collaborators Jun 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant