Currently the CPU CI takes a very long time to run, eg:
https://github.com/NumericalEarth/NumericalEarth.jl/actions/runs/25079084434/job/73485468142?pr=149
It also seems to test data downloading (?) which overlaps with the data downloading GHA jobs.
Do we have an idea why GPU tests are much faster? Usually GPU takes longer because of longer compile; however in this case the CPU for CPU tests and CPU for GPU tests are very different (since compile happens on CPU).
We could consider reducing the CPU testing while keeping GPU more complete. Or maybe there are other strategies to speed up the CPU tests.
Currently the CPU CI takes a very long time to run, eg:
https://github.com/NumericalEarth/NumericalEarth.jl/actions/runs/25079084434/job/73485468142?pr=149
It also seems to test data downloading (?) which overlaps with the data downloading GHA jobs.
Do we have an idea why GPU tests are much faster? Usually GPU takes longer because of longer compile; however in this case the CPU for CPU tests and CPU for GPU tests are very different (since compile happens on CPU).
We could consider reducing the CPU testing while keeping GPU more complete. Or maybe there are other strategies to speed up the CPU tests.