Jest prints superfluous warning when ran with '--passWithNoTests' and there are no tests

[kaykayehnn]

🐛 Bug Report

When jest runs but there are no tests to execute, by default it exits with code 1 (error) and prints the following message

No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In /path/to/my/project
  1 file checked.
  testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 0 matches
  testPathIgnorePatterns: /node_modules/ - 1 match
  testRegex:  - 0 matches
Pattern:  - 0 matches

When running with --passWithNoTests, jest exits with code 0 but the same message gets printed.

Expected behaviour

Jest does not print warning when ran with --passWithNoTests

Actual behaviour

Jest prints warning when ran with --passWithNoTests

To Reproduce

In an empty directory:

1. yarn add jest
2. Add "test": "jest --passWithNoTests" to scripts in package.json
3. yarn test

Link to reproducible repo

kaykayehnn/jest-pass-with-no-tests-bug

Environment

  System:
    OS: macOS 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
  Binaries:
    Node: 12.4.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.1-next.0 - ~/.npm-global/bin/npm
  npmPackages:
    jest: ^24.8.0 => 24.8.0

I can submit a PR for this if that's okay.

[thymikee]

PRs always welcome :)

[github-actions]

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.