Getting more debug information from between pytest call and start of tests? #12957
-
Hey there, over at Manim we are having a hard time getting our test suit to run properly on a GitHub Actions runner with the Unfortunately, I can't really reproduce this on a local device, so I am more or less stuck with debugging using the runner. I've tried quite a bunch of things that I could think of to get more detailed information -- for example, here is a run of In my latest attempt I tried to trigger consistent pytest errors (during testing) by removing one of the fixtures we use, see https://github.com/ManimCommunity/manim/actions/runs/11788149689/job/32834760283 -- all OS / python version combinations behave as expected, except for our pathological case where the runners appear to experience hard crashes. Something about this combination seems quite cursed. I've not found anything explicit in pytest's documentation (but I might have overlooked it, of course): is there any way to get more debug information for the case where pytest exits prematurely? Or is this perhaps a known issue? I'd be very happy and grateful for any sort of general pointers; thank you very much for your efforts! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The The flag combination Also, take a look at the built-in faulthandler plugin |
Beta Was this translation helpful? Give feedback.
The
PYTEST_DEBUG
environment var triggers excessive debug outputThe flag combination
-sv
may suffice to pin it downAlso, take a look at the built-in faulthandler plugin