CI: Pin PYTEST_WORKERS=1 for Windows builds due to memory errors
1. Running tests without xdist is okay
2. It's not due to pyarrow v8 (I think)
3. Same error with `windows-2019` as `windows-latest`
im not seeing a way to download the log file (which is too big to display in the browser) > im not seeing a way to download the log file (which is too big to display in the browser)

https://github.com/pandas-dev/pandas/suites/6902339888/logs?attempt=2 is the direct download link for the 3.9 build Looks like you're doing trial/error to figure out what test is failing?  LMK if i can be helpful > Looks like you're doing trial/error to figure out what test is failing? LMK if i can be helpful

Yeah, I think there's a memory leak somewhere but for now I'm just skipping tests to hopefully skip the one that leaks. If you have time/ideas how to identify the leaking test(s) that would be helpful  @jbrockmendel the first PR merged into main that exhibited these failures was https://github.com/pandas-dev/pandas/pull/47299. If you have a chance could you comb over that PR again to see if any change there could cause a memory leak? The changes in tzconversion.pyx are the most plausible candidate, though
not a slam dunk

On Sun, Jun 19, 2022 at 1:27 PM Matthew Roeschke ***@***.***>
wrote:

> @jbrockmendel <https://github.com/jbrockmendel> the first PR merged into
> main that exhibited these failures was #47299
> <https://github.com/pandas-dev/pandas/pull/47299>. If you have a change
> could you comb over that PR again to see if any change there could cause a
> memory leak?
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/pandas-dev/pandas/pull/47318#issuecomment-1159805646>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AB5UM6AXF6OJIHNI4KNSIPDVP57BVANCNFSM5YSCUS4A>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
 lgtm to get ci green(ish) for now. @simonjayhawkins should we backport to 1.4.x or just merge to main? probably should backport as could miss things when ci is not green? Okay merging to get the CI back to green for Windows builds sure. have not seen windows failures on 1.4.x but if we don't know the root cause then no harm.