chore: add a per test 3min timeout and enable color output

[bringhurst]

Why is this needed?

It's difficult to reproduce, but I've seen the github actions test suite take more than 6 hours. Having a timeout set will allow us to get some sort of useful debug information instead of having github actions kill it off before we can analyze anything.

Proposed Changes

• Do not allow any one unit test to take more than an hour. If it takes longer than an hour, kill it off and print some basic debug info (e.g. a stack trace of all/most frames).
• Enable color pytest output to make pytest easier to read in general.

Does this PR introduce any breaking change?

No -- this is intended to help debug the test suite.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (55f27b2) 96.76% compared to head (5bdd8ee) 96.79%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #700      +/-   ##
==========================================
+ Coverage   96.76%   96.79%   +0.02%     
==========================================
  Files          27       27              
  Lines        3557     3557              
==========================================
+ Hits         3442     3443       +1     
+ Misses        115      114       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[bringhurst]

I keep seeing this error also (it appears to be a string returned from the codecov api):

Could not determine repo and owner

Setting codecov-actions to verbose doesn't seem to give any more details.

🤔

[ceache]

I think the timeout is ok. If the tests did not complete in 1h, they are not going to complete ever.

…

On Sun, Jan 29, 2023, 16:17 Jon Bringhurst ***@***.***> wrote: I keep seeing this error also (it appears to be a string returned from the codecov api): Could not determine repo and owner 🤔 — Reply to this email directly, view it on GitHub <#700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIFTHSG3HX2FDX6GV7XPXTWU3M6FANCNFSM6AAAAAAUKOK74U> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[a-ungurianu]

This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

I wonder if this is why you see the codecov things, as it tries leverage the Github App.

@ceache I don't have the rights to add the app. Do you know someone who does?

[bringhurst]

An example of this showing useful debug output:

https://github.com/python-zk/kazoo/actions/runs/4038897905/jobs/6943223749

It lets the pytest timeout (not github actions timeout) determine that the test failed and prints out a trace of all frames.

[bringhurst]

It looks like this job may time out -- https://github.com/python-zk/kazoo/actions/runs/4039044495/jobs/6943463553

If that works correctly (times out and shows stack traces), I'll open this up for review.

Edit: It looks like this shows a nice stacktrace.

[jeffwidman]

Happy to try it, and keep it as long as it's useful!

I do wonder whether this is just actions infra being flaky from time to time, or if we've got some bugs in our code that are hiding... could just be Zookeeper occasionally flaking as it comes up, I know I've seen that from time to time although no idea if that's Zookeeper, or Docker or something else...

[StephenSorriaux]

I have resurrected this PR and reduced the timeout from 1h to 3min since it is a per-test timeout.

@jeffwidman @a-ungurianu @ceache if you have some time to check it

[jeffwidman]

Looks great 👍