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

[Bug]: don't use workers in watch mode if --runInBand is specified #14530

Closed
cdoublev opened this issue Sep 15, 2023 · 2 comments · Fixed by #14578
Closed

[Bug]: don't use workers in watch mode if --runInBand is specified #14530

cdoublev opened this issue Sep 15, 2023 · 2 comments · Fixed by #14578

Comments

@cdoublev
Copy link

Version

29.7.0

Steps to reproduce

  1. Clone https://github.com/cdoublev/jest-issue
  2. Run node --inspect-brk=0.0.0.0:9222 ./node_modules/.bin/jest --watchAll --runInBand (or npm test)
  3. Open chrome://inspect/ in Chrome
  4. Click inspect in the target list

Expected behavior

I expect the code to break at the debugger line in ./add.js.

Actual behavior

The code did not break.

Additional context

Follow-up on #14085 (comment).

Environment

System:
  OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
  CPU: (1) x64 Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz
Binaries:
  Node: 20.5.1 - /usr/bin/node
  npm: 9.8.0 - /usr/bin/npm
npmPackages:
  jest: ^29.7.0 => 29.7.0
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2023
@SimenB
Copy link
Member

SimenB commented Oct 30, 2023

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants