CI tests way too long on WIndows !

[gmaze]

We need to understand why CI tests are so much longer with Windows OS than with the other Linux and Mac.

They can take longer than the runner cancelling policy of 45mins, eg:

https://github.com/euroargodev/argopy/actions/runs/11027230679/job/30627964822

which make the CI tests suite to fail for the wrong reasons

Any idea of how to improve this or to understand why this is the case ?

[gmaze]

and yes, fail-fast is set to false on the workflow

[gmaze]

stupid me: timeout-minutes: 45 !

[gmaze]

why did we set such a time out ?

[gmaze]

well, that does not explain why CI tests remain much slower on Windows

[ocefpaf]

I did look at your setup but Windows have some aggressive file locking that can make some IO operations quite slow. Sometimes creating the environment is the bottleneck, and if that is the case here, I wonder if pixi could help. I can try a PR n xt week if you are interested in experimenting with it.

[gmaze]

thanks @ocefpaf !
let me check first if the env is the bottleneck

[gmaze]

building/restoring the env with micromamba takes about 5mins in Windows, while is takes 1mins (build) or 15 seconds (restore from cache) under Linux and Mac OS, even if the env is in cache and about the same size (600 vs 500 mb)

as an indication, the tests suite takes about:

• 30mins to run under Linux
• 25mins under Mac Os
• 50mins under Windows

so even if we install the env in about seconds, running the suite under Windows remains slower by about 15 to 20 mins