Jason Madden

I don't have any solutions for you but I can make some observations and suggest some possibilities. If you know statically what code sections you want to avoid switching, and...

The same goes for `gevent/tests/known_failures.py`.

Working on #1401 made me truly realize how large our potential configuration space and hence test matrix is: (4 interpreters x 3 backends x 3 resolvers x 2 files) +...

There appear to be two basic failures. The first is that things that are expected to be fast are sometimes very slow. This has been seen to be the case...

Oh, also the `test__threading_monkey_in_thread` failure is specific to 3.9.8+ because of a change in CPython (#1839); I haven't been able to release a fix yet. It's a legitimate failure that...

I assume that `to_dataframe()` is CPU bound. gevent can't make CPU bound functions switch and cooperate with the event loop. You can move CPU bound functions outside of gevent's loop...

Fixed as-of 275b7d977cf48d5ee2edee8c360e015369e55497, with the same caveats as the aarch64 binaries: I do not recommend them for anything other than development.

I don't think GitHub Actions can do that. A PR that proves me wrong would be welcome.

Thanks for this PR! I apologize for the delayed response, I've been fully occupied with other projects. I'll get back to this as soon as I can.

This changed in [1.5a2](https://github.com/gevent/gevent/commit/9d27d269ed01a7e752966caa7a6f85d773780a1a#diff-5c1fac58666e8444f93264107cb96915fe63966d46459770fe5bc06585d50a35) to deal with timeouts apparently caused by buffering. Tests would need to be added to use that type of socket (being sure not to run them...