imod.tests.test_mf6.test_mf6_regrid_model.test_model_regridding_can_validate and imod.tests.test_mf6.test_mf6_regrid_model.test_model_regridding_can_skip_validation both take nearly 1 minute. These are the longest tests so far in the pipeline
There are a lot of tests for splitting and partitioning. We should investigate if we can coarsen grid for these test cases to speed up times.
If this is not doable, we can consider creating a separate pipeline for all the multimodel tests, which can run in parallel.
Alternatively: We can adapt our test strategy and include certain slower tests in a nightly pipeline. In this way changes which break things are not directly identified, but still be traced back to the day of a breaking commit.
The unittests take too long; locally on my machine ~15 minutes but on TeamCity they approach 45 minutes.
Looking at this example, I observe the following things:
imod.tests.test_mf6.test_mf6_regrid_model.test_model_regridding_can_validateandimod.tests.test_mf6.test_mf6_regrid_model.test_model_regridding_can_skip_validationboth take nearly 1 minute. These are the longest tests so far in the pipelineIf this is not doable, we can consider creating a separate pipeline for all the multimodel tests, which can run in parallel.
Alternatively: We can adapt our test strategy and include certain slower tests in a nightly pipeline. In this way changes which break things are not directly identified, but still be traced back to the day of a breaking commit.