Open oliver-sanders opened 3 years ago
See comment on this issue https://github.com/cylc/cylc-flow/pull/4197 about building images with both pip/conda to test dependency changes.
Elaboration on the above comment...
conda-environment.yml
.conda-pack
this into a tarball./bin/
execs with links to the Conda bin/
but that's messy.pip install -e
the cylc-flow repo.We then dispose of the first container (job done).
Related:
3372
3935
3936
The Docker “swarm” used by the test battery uses containers to emulate remote job platforms and runs the tests themselves on the local platform.
This largely replicates the old system; it allows us to run the test battery on the system it will be deployed on including the job platforms available which is very useful.
However:
I suggest that we make it possible to run the whole test battery in containers where desired whilst still supporting running tests locally. We can then install and configure the job runner stuff on these images allowing testing of slurm, pbs, etc. You wouldn’t be able to use these containers from your local system (without doing the heavy lifting yourself) but would still be able to use the background/at containers as well as available platforms for local testing.
Something along these lines: