To address some problems with certain tests not currently working under Pants vs the current environment (probably related to parallelism?) I tried defining two

python_tests

in the directory that has the tests in question... 🧵

python_tests(
  name="test",
  source=[
    "test_*.py",
    "!test_that_is_deadlocking1.py",
    "!test_that_is_deadlocking2.py"
  ]
)

python_tests(
  name="deadlocking_tests",
  source=[
    "test_that_is_deadlocking1.py",
    "test_that_is_deadlocking2.py"
  ]
)

path/to/dir::

rather than

::path/to/dir

If I run

./pants test test::

I'm still seeing

Run Pytest for test/something/something/test_that_is_deadlocking1.py:deadlocking_tests

oh wait yeah that's expected -

test::

means all matching targets recursively under the dir

test

. If you want to run all those targets except for some, you could use tags https://www.pantsbuild.org/docs/advanced-target-selection#tags-annotating-targets (i also have a proposal to add ignore specs like

test:: !test/subdir::

)

I'd like to use tags, but https://github.com/pantsbuild/pants/issues/14977 😉

@rapid-exabyte-76685: fwiw, given that you have split into two generators like that, i think that tags should work fine. https://github.com/pantsbuild/pants/issues/14977 only affects

overrides

, afaict.

yep that does indeed work 👍 much cleaner than a

--spec-file