We have a default timeout of 60 seconds in our

pytest.ini

file. I know this value is being respected because I can change it and see things break when I set a silly low timeout value. For some reason, we had a test hang for a crazy long time in CI without catching it. Anyone ever seen anything like this? This one uses a pytest fixture. Maybe that time isn't included in timeout consideration?

23:40:24.23 [INFO] Long running tasks:
  3315.53s	Run Pytest for astranis-python/astranis/ground/monitoring/managers/configuration_manager_test.py:tests

If you're looking for a workaround, are you aware you can set a global timeout in pants that'll abort the whole test run, at a process level? https://www.pantsbuild.org/docs/reference-test#timeout_default Potentially more reliable in terms of stopping runaway test invocations.... but does nothing to provide insight into why it might happen.

That's definitely nice as a last effort safety switch. Just a little more concerned that this just ran away on its own. The only explanation I could have is that it's inside the pants logic and that test execution was actually done in a reasonable amount of time.