Speed up CI tests

[patrickersing]

With the additional features being added having a single CI job became very slow.
This PR should speed up the CI time by splitting the tests into multiple jobs. Furthermore, macOS and windows tests will run without coverage and become restricted to the upstream testset.

[andrewwinters5000]

With the additional features being added having a single CI job became very slow. This PR should speed up the CI time by splitting the tests into multiple jobs and also restricts the coverage testing to ubuntu.

This is a good idea to make the CI faster. Should we already drop back the macOS version here as discussed in #40?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.22%. Comparing base (71bba1e) to head (96962a8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   99.22%   99.22%           
=======================================
  Files          45       45           
  Lines        1680     1680           
=======================================
  Hits         1667     1667           
  Misses         13       13           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[patrickersing]

With the additional features being added having a single CI job became very slow. This PR should speed up the CI time by splitting the tests into multiple jobs and also restricts the coverage testing to ubuntu.

This is a good idea to make the CI faster. Should we already drop back the macOS version here as discussed in #40?

I think this will not be necessary, since in this setup we would no longer do coverage testing on macOS. Since the problem in #40 only appeared in the coverage tests I expect that this would fix the problem.

[andrewwinters5000]

With the additional features being added having a single CI job became very slow. This PR should speed up the CI time by splitting the tests into multiple jobs and also restricts the coverage testing to ubuntu.

This is a good idea to make the CI faster. Should we already drop back the macOS version here as discussed in #40?

I think this will not be necessary, since in this setup we would no longer do coverage testing on macOS. Since the problem in #40 only appeared in the coverage tests I expect that this would fix the problem.

Ah, gotcha. Then this sounds doubly good if it provides a workaround for the issues encountered on Mac-ARM.

[patrickersing]

This provides a good speedup from the single job tests that previously ran for over 30min.
For additional speed we could also separate the coverage tests into it's own job.
However, the checks become a bit crowded now as we test everything on macOS, windows and ubuntu.
@andrewwinters5000 What do you think about restricting the macOS and windows tests to the upstream testset, which should cover the most important features of TrixiSW?

[andrewwinters5000]

This provides a good speedup from the single job tests that previously ran for over 30min. For additional speed we could also separate the coverage tests into it's own job. However, the checks become a bit crowded now as we test everything on macOS, windows and ubuntu. @andrewwinters5000 What do you think about restricting the macOS and windows tests to the upstream testset, which should cover the most important features of TrixiSW?

That might be for the best, especially because it avoids the need to adjust the tolerances for the wet/dry well-balancedness tests on macOS which I see are failing due to round-off differences.

[patrickersing]

Okay, I have restricted macOS & windows testing to upstream and separated the coverage tests.

[andrewwinters5000]

LGTM! Thanks for speeding up the CI testing. I think we need to change the branch protections to reflect the new structure instead of the tests like Julia 1.10 - macOS-latest - x64 - pull_request that no longer exist.

[patrickersing]

LGTM! Thanks for speeding up the CI testing. I think we need to change the branch protections to reflect the new structure instead of the tests like Julia 1.10 - macOS-latest - x64 - pull_request that no longer exist.

Yes, branch protection still needs to be updated. Can you take care of this? I don't have sufficient rights.