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’ve noticed that we have tests in CI timing out that do not take anywhere near that timeout when run standalone

Before I dive into this, I assume we’re confident that the Process timeout applies when the process starts running, not when it’s queued or something?

So the issue is, potentially, starvation due to actual CPU contention, and not just something silly with the timeout?

but yes: for local processes, it’s only after we’ve actually spawned the process.

Sometimes it looks like network, but in the cases I’ve been looking at recently it seems like it’s not