mamba saved my CI
We moved from Azure to github actions to run the continuous integration tests in PopPUNK about a year ago. It’s been working pretty well and wasn’t too bad to set up, and integrates nicely into the pull requests.
However, in the past month two things happened:
joblibv1.2 introduced a breaking security change which meant thathdbscanerrored. Solving a conda environment pinningjoblibto 1.1 takes about 12 hours (😱) to solve (longer than the 4 hour github limit).- Even without the pin, environment resolution increased from about an hour to 3-4hrs, so the CI would only sometimes run.
Fixing conda on the CI
About 4/5 years ago I’d tried using mamba as a replacement for conda. It worked really well and was much faster, but I’d since read that some of its techniques were being merged into conda, and in general I stopped having hugely long times while solving the environment. But times seemed to be getting longer again (especially on the CI, not sure why), and I think mamba actually remains fundamentally different to the conda solver.
