You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems to be due to a problem in conda with concurrent parallel environment creation (not present when using mamba). See nextflow-io/nextflow#4464 (comment)
The problem with the environment names is that they affect the container URIs generated by Wave, and so Seqera Containers. This reduces the ability for caching and reuse.
As we move away from pytest-workflow to nf-test we can safely remove these and simply deprecate pytest-workflow. It's unclear how common the error is for end users. The above Nextflow comment suggests that it may happen for some users with shared Nextflow instances on HPC, though these are probably relatively few in number and can be easily overcome by using mamba instead.
The text was updated successfully, but these errors were encountered:
The conda
environment.yml
files that we use currently define aname
attribute:These were added in #4327 to fix an issue that we had cropping up with pytest-workflow for nf-core/sarek (see #4234):
This seems to be due to a problem in conda with concurrent parallel environment creation (not present when using mamba). See nextflow-io/nextflow#4464 (comment)
The problem with the environment names is that they affect the container URIs generated by Wave, and so Seqera Containers. This reduces the ability for caching and reuse.
As we move away from pytest-workflow to nf-test we can safely remove these and simply deprecate pytest-workflow. It's unclear how common the error is for end users. The above Nextflow comment suggests that it may happen for some users with shared Nextflow instances on HPC, though these are probably relatively few in number and can be easily overcome by using mamba instead.
The text was updated successfully, but these errors were encountered: