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

Pants

image.png

Q. Could I reduce the time for running pytest in GitHub Actions as it seems to spend much time on build pex requirements?

The tests usually takes 5-7 minutes, and 2-3 minutes are consumed by these steps.

have you seen <https://www.pantsbuild.org/docs/using-pants-in-ci> ?

Yes, I've already getting benefits from `--changed-since` and `actions/cache` as guided with inclusion of `pants.toml` and `*.lock` in `hashFiles()`.

Though, the pex initialization step (this is irrelevant to `--changed-since`) in pytest takes too long, while lint/check initialization steps complete almost instantly. (I also know that the slowness of running mypy against hundreds of files is <https://github.com/pantsbuild/pants/issues/10864|another issue>)

So GitHub actions will start deleting stuff when your cache hits 10gb. So you might want to see if that is happening (not sure if they have a ui for that) but at the very least the logging from the GHA cache actions should give you some idea of the cache sizes that are moving 