This seems to only occur for my Python 3.7 job, but I don’t want to read too much into that.
As you can see in the output, pytest runs and reports its test summary, but for some reason CircleCI is still “waiting for output”. This seems to be happening more and more frequently for us, and I’m not sure how to even begin debugging this.
Any insights / help would be appreciated - thanks!
Perhaps the tests create new processes in memory, and CircleCI is waiting for them to close down?
You could temporarily force your tests to look like they have passed pytest --cov=prefect . || true and then have a separate run step ps aux to see what processes are in memory.
Is it intermittent with Python 3.7, or does it happen every time with that version?
It appears that adding || true prevents this behavior from happening… it looks weird but that makes me wonder if I should just do pytest --cov=prefect . || false…
Oh and for the record, this was the output of ps aux everytime:
It seems then that pytest is failing to register an exit code for some reason related to CircleCI (I can’t reproduce this inside a python:3.7 docker container).