[all-commits] [llvm/llvm-project] 49b209: [lit] Remove the --no-indirectly-run-check option

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 49b209d5cca3750f71e8a6fda1c5870295ef3a9c
      https://github.com/llvm/llvm-project/commit/49b209d5cca3750f71e8a6fda1c5870295ef3a9c
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2023-07-17 (Mon, 17 Jul 2023)

  Changed paths:
    M llvm/docs/CommandGuide/lit.rst
    M llvm/utils/lit/lit/LitTestCase.py
    M llvm/utils/lit/lit/cl_arguments.py
    M llvm/utils/lit/lit/discovery.py
    M llvm/utils/lit/lit/formats/base.py
    M llvm/utils/lit/lit/main.py
    M llvm/utils/lit/tests/discovery.py
    M llvm/utils/lit/tests/unit/TestRunner.py

  Log Message:
  -----------
  [lit] Remove the --no-indirectly-run-check option

This option had originally been added in D83069 to allow disabling the
check that something is going to get run at all when a specific test name
is used on the command-line. Since we now use getTestsForPath() (from D151664)
to get the tests to run for a specific path, we don't need a specific check
for this anymore -- Lit will produce the same complaint it would produce if
you provided a directory with no tests.

If one needs to run a specific test on the command-line and the Lit
configuration would normally not include that test, the configuration
should be set up as a "standalone" configuration or it should be fixed
to allow for that test to be found (i.e. probably fix the allowed test
suffixes).

Differential Revision: https://reviews.llvm.org/D153967