[skip azp][skip circle][skip cirrus]

Fixes #25708, apparently it is enough to disable progress bars. Maybe we should do this globally with a PIP_CONFIG_FILE, I doubt anyone enjoys seeing the progress reports in CI.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, now it seems stuck on 63% of tests

FFT crashing in some thread-safety tests (the test that should run next) does seem like it may be an actual new issue? Ping @mhvk, although not sure if you are likely to have much insight.

If that is the case, it might make sense to just put this in anyway...

Maybe we should do this globally with a PIP_CONFIG_FILE, I doubt anyone enjoys seeing the progress reports in CI.

I'm not sure why, since there has never any problem before and in principle progress bar output in pip is there to avoid timeouts (zero output for a long time may cause CI to kill a job). Don't touch it unless there's a problem beyond Cygwin I'd say.

Agreed that this seems fine to merge as is. What could be useful to check if the fft hang is new or a coincidence is to rebase this progress bar fix to before all the fft changes on a separate branch and trigger the Cygwin job on that branch.