CI: 310-dev build seems to be timing out

[jreback]

xref https://github.com/pandas-dev/pandas/runs/3990827693?check_suite_focus=true

not sure where this changed recently or a numpy issue.

[jreback]

cc @jbrockmendel any ideas here

[jbrockmendel]

looks like it is stalling somewhere in the network tests, which is also where the windows stalls usually are. thats all i got

[jbrockmendel]

xref #43611 not sure if @mzeitlin11 figured out what was going on there

[jreback]

ok let's disable these for now then. its super hard to see failures w/o green (well its not that hard but it takes a lot of time).

[mzeitlin11]

xref #43611 not sure if @mzeitlin11 figured out what was going on there

In that case it also looked like network tests, but ended up actually being deadlocks in pyarrow read_csv (#43650). Certainly possible there are other cases that deadlock that weren't found and skipped in the initial pass. I'll try running with the logging setup in #43611 and see if anything turns up (sidenote is there a way to just trigger the 310-dev to run?)

[jreback]

you can comment out parts of the ci config to turn it off temporarily

[mzeitlin11]

In #44183, both ubuntu and macos timed out. Filtering the logs to contain only lines with moments gives the attached file (warning still 15.3 MB :).
clean_mac_out.txt

Based on this, tests in pandas/tests/window/moments/ start running at 00:19:15 and end at 00:47:31 (at which point the timeout happens). Will run again to see if the same result happens. These tests run locally on macOS for me in < 2.5 min (with the same logging enabled)

[jreback]

cc @mroeschke let's move back some of the moved tests

[Dr-Irv]

MIght be that we have to split the tests in half like I did in #43517 and #43468

[mroeschke]

@jreback moving back the tests in my recent PRs wouldn't make a difference since all tests in pandas/tests/window are run on macOS and Ubuntu (tests in pandas/tests/window/moments are only ignored on Windows #37535).

There's a lot of tests in pandas/tests/window/moments that are redundant with tests in pandas/tests/window/test_*.py that I am working on thinning out. As a short terms fix, you can skip the pandas/tests/window/moments I suppose while I am improving the performance of those tests.

https://github.com/pandas-dev/pandas/runs/3990827693?check_suite_focus=true specifically looks to specifically end on a test that uses the moto_server (s3_base fixture)

[jreback]

kk can i push a PR to skip these in 3.10?