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

Pants

I'm trying to optimize LFS pulls in tests, by fixtures that run `git lfs pull --include=...` only for required files only when required by selected tests. The problem is that when running `pants test`, it is run inside an isolated pex environment, so there is no `.git` directory to run `git` against. Would there be a solution for this?

If I run `git lfs pull` command on the build root, Pants detects filesystem changes and interrupt + retry running the test module. This makes the CI to pass, but I'm now worried about the future: what if there are multiple test modules depending on the same LFS file and races between them?

One idea would be working out which tests _will_ run and running the relevant `git lfs` for only those tests, all outside the `pants test ...` invocation

I am a newb at this, but could the tests depend on an adhoc call for git lfs?