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.

Sign up for GitHub

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

Jump to bottom

[Bug]: runInBand not respected via config file #14855

Closed
sezanzeb opened this issue Jan 15, 2024 · 6 comments · May be fixed by #14857
Closed

[Bug]: runInBand not respected via config file #14855

sezanzeb opened this issue Jan 15, 2024 · 6 comments · May be fixed by #14857
Labels
Bug Report Needs Triage Stale

Comments

@sezanzeb
Copy link

sezanzeb commented Jan 15, 2024 •
edited

Version

29.7.0

Steps to reproduce

  1. Add "runInBand": true to your config file (for example jest.config.cjs)
  2. Run tests

Expected behavior

For runInBand to be respected when provided to the config

Actual behavior

● Validation Warning:

  Unknown option "runInBand" with value true was found.
  This is probably a typing mistake. Fixing it will remove this message.

  Configuration Documentation:
  https://jestjs.io/docs/configuration

Additional context

runInBand only works as cli argument. It is also not present in the docs for config files: https://jestjs.io/docs/configuration#workerthreads

Other people have observed this as well: https://stackoverflow.com/a/67935087/4417769

The workaround is to use "maxWorkers": 1

Environment

System:
    OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)
    CPU: (12) x64 AMD Ryzen 5 5500U with Radeon Graphics
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm
@WillianAgostini WillianAgostini mentioned this issue Jan 16, 2024
Open
@WillianAgostini
Copy link
Contributor

I perceive this as a feature request, as it implies the inclusion of a new field. Nevertheless, I've opened the PR #14857 to incorporate this new field into the configuration file.

@sezanzeb
Copy link
Author

cool, thanks

@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Feb 15, 2024
@github-actions GitHub Actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

1 similar comment
@github-actions GitHub Actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 16, 2024
@github-actions 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 Apr 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug Report Needs Triage Stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: include 'runInBand' configuration WillianAgostini/jest
2 participants
@WillianAgostini @sezanzeb