CI is sloooow

[axelboc]

You've probably noticed it. Not sure if it's a temporary slow down or if it's something to do with the recent change to test all supported Python versions. https://github.com/mxcube/mxcubeweb/actions/runs/11069955541

[marcus-oscarsson]

I think its temporary, it was quite quick earlier today. The pages build took forever though.

[fabcor-maxiv]

Nothing obvious on https://www.githubstatus.com/

[marcus-oscarsson]

Looks like the actions are stuck on

micromamba list
  /home/runner/micromamba-bin/micromamba list -r /home/runner/micromamba -n mxcubeweb

A bit strange, considering that is just listing the installed packages. It does not seem to matter if we are only running one python version or several simultaneously

[fabcor-maxiv]

There was a new major release of mamba and micromamba. Versions 2.0.0 for both. Maybe something broke.

We can try:

- uses: mamba-org/setup-micromamba@v1
  with:
    micromamba-version: '1.5.10-0' # any version from https://github.com/mamba-org/micromamba-releases

[fabcor-maxiv]

mamba-org/setup-micromamba#225

[marcus-oscarsson]

I think thats it !

[fabcor-maxiv]

I am a bit reluctant to make a fix for it that would involve pinning the version of micromamba...

• If we are lucky, there will be a fix in micromamba (or the setup-micromamba action) soon enough.
• Do we really want to pin the version of micromamba? Would dependabot help us keep the pinned version up to date?

[fabcor-maxiv]

For info:

Looks like in principle the root issue has been fixed and the fixed version has been released (in version 2.0.1):

• fix: Handle MatchSpec with brackets when parsing environments' history mamba-org/mamba#3490
• https://github.com/mamba-org/mamba/releases/tag/2024.09.30
• micromamba list runs indefinitely on Micromamba v2.0.0 mamba-org/setup-micromamba#225 (comment)

So I assume that in principle we could remove the pin (I have not tried it). On the other hand, maybe it is not a bad idea to wait a bit longer until micromamba v2 is more stable in general.