CI: Troubleshoot
- [ ] closes #xxxx
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them
- [ ] whatsnew entry

My theory proved incorrect in https://github.com/pandas-dev/pandas/pull/45500. Looks like you're having more luck here? looks like azure is green.  time to whittle these down... great any luck here? can we force the windows builds to a single cpu? (and maybe disable some expensive tests / keep 2 builds) > any luck here?

slowly narrowing it down OK! looks like its somewhere in usecols... im bashing my head against the wall here, need to tag someone else in on this can we look at the past CI runs when we were green and see what changed in the config? The build that just failed is almost identical to one that passed a few hours ago (see the "remove usecols" commit above 71bf824).  That commit also removed the entire usecols directory, while this one left `usecols/__init__.py` > can we force the windows builds to a single cpu? (and maybe disable some expensive tests / keep 2 builds)

Trying this approach in https://github.com/pandas-dev/pandas/pull/45547. The CI is really backed up right now so it might take a while to get to > The CI is really backed up right now so it might take a while to get to

Could/should we just cancel some of the non-fixing-this azure jobs to speed this up? > > The CI is really backed up right now so it might take a while to get to
> 
> Could/should we just cancel some of the non-fixing-this azure jobs to speed this up?

Yeah if there are lot of queued up jobs it would allow to debug this quicker. But looks like the queue cleared up overnight azure green! > azure green!

Confident it was this or do you think retriggering the CI will confirm this? ok let's merge on green (i retriggered) let's also an issue to troubleshoot this as well (this case you are skipping) @meeseeksdev backport 1.4.x Something went wrong ... Please have a look at my logs.