A community effort to collect a curated set of analysis pipelines built using Nextflow.

nf-core

<https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/21M6pUgGDUj0rs/v2/logs>

```7:23AM INF instance metadata ami-id=ami-076452d1c290afa09 instance-id=i-02cd9318aa3da0117 instance-type=m6id.4xlarge
tmp_dir: /fusion/s3/nf-core-awsmegatests/work/bamtofastq/work-dev/83/32645ad4027d3e7a7b280a117d5596/.fusion/tmp
pid signal: 1
caught termination signal! exiting...
pid signal: 40
caught termination signal! exiting...
Fusion Info:
    clone_namespace: false
    kernel_version: 6.1
    disk_cache_size: 884Gb
    max_open_files: 1048576
    fusion_version: 2.4.13-cd14732```

which seems HIGHLY similar to this error message: <https://nfcore.slack.com/archives/C04QR0T3G3H/p1748008750690949>

somthing is broken on the megatests submission. the results directory for the release ends on dev

why are the full size test not run on the release?

doing this check with s3 for bigger files is no good

that's what was triggered by the megatests

<https://github.com/nf-core/tools/pull/3583>

oooh, that test was not the megatests megatests but the megatests not megatests

<@UQZG2UCF3> are you saying that this should have been run on the new release tag and not on `dev`?

<@UE6D8290F>, I have no idea what's going on :laughing:

i don’t know the full context, but because you were talking about megatest and release and something broken, I thought it was related to this, but if it is from the `dev` channel then :homer_disappear:

Ok we need Maxime to clarify if this run was triggered on the release action -&gt; bug in tools because it picked `dev` instead of the release tag

Given the timing, I assumed it was triggered by the release action, because I didn't trigger it, and <@U065DAZ0PL5> forgot about it

and then related to what <@UEM37TBAR> was talking about this morning

I checked all recent releases and we all had the same issue

Mag, bamtofsstq and ampliseq

Release job was being skipped on GitHub actions

At least I ran the full size tests locally and they completed without issues so I forgot that there is the AWS one :sweat_smile: