After #1104 was merged recently it broke all MPI tests of nextsim due to a misconfiguration in the Dockerfile (incorrectly set environmental variable).
This exposed the problem that we currently have no way to assert if the new versions of the containers do not break CI without merging them in. Building the code and running the tests manually may not be enough since GitHub CI seems to have its own subtleties. In case of #1104, the environmental variable set in ENTRYPOINT script did not propagate correctly to steps of the GitHab actions job in test_suite workflow.
Ideally we should run XOIS+MPI test job on the freshly build container as part of the Docker CI, but I don't know yet how to configure it (or if it is even possible)
After #1104 was merged recently it broke all MPI tests of nextsim due to a misconfiguration in the Dockerfile (incorrectly set environmental variable).
This exposed the problem that we currently have no way to assert if the new versions of the containers do not break CI without merging them in. Building the code and running the tests manually may not be enough since GitHub CI seems to have its own subtleties. In case of #1104, the environmental variable set in
ENTRYPOINTscript did not propagate correctly to steps of the GitHab actions job intest_suiteworkflow.Ideally we should run XOIS+MPI test job on the freshly build container as part of the Docker CI, but I don't know yet how to configure it (or if it is even possible)