Consider updating 'coverage' to address CI failures

[eddyg]

While looking at the test failures for #1283, I came across this issue in pytest coveragepy which seems like it could be applicable.

A fix was committed in pytest 6.4; might be worth bumping the dependency to see if it improves the reliability of the CI builds.

[seratch]

Hi @eddyg, perhaps you meant coverage v6.4+, right? pytest v6 does not exist. The CI builds in this repo can sometimes be unstable due to the following reasons:

• Unstable behaviors of GitHub Actions containers
• The load tests for SocketModeClient tend to fail

I am unsure if we should upgrade coverage package for it but we are always happy to upgrade the packages for tests at any time.

[eddyg]

Yes, I did indeed mean coverage. 🤦

The reason that issue sounded like it could be applicable is that when I would review the CI failures, I would often see them "cancelled" at the point where the last thing in the logs was running pytest --cov.

See, for example, these failures: one • two • three

But perhaps "correlation is not causation" in this case. It seems like you're aware of the CI being "flakey".

Please feel free to close this issue!

[seratch]

@eddyg Thanks for your reply! I've improved the load test for SocketModeClient yesterday. The tests still sometimes fail but I believe that the frequency was much improved. We will continue improving the stability of tests. Let me close this issue now.