Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

It seems like our custom markers defined in `pytest.ini` are sometimes getting ignored by pants and pants is complaining that the markers aren't defined. Not sure how best to reproduce at the moment. I just did a whole run pointing to the problem test with `./pants --no-local-cache path/to/my/marked_test.py` and pytest didn't complain. However, on our build system, I've noticed a few times now where it does complain about the marker being undefined.

Hmm, the pytest rules should auto-discover pytest.ini and put it in the sandbox

Weird that it's not happening consistently

Turns out I didn't have `pytest.ini` unignored in my `pants_ignore` in `pants.toml`. I'm confused how it could ever work though now :thinking_face:

It was originally ignored cause we did a blanket policy and have been unignoring things as needed for incremental adoption purposes.