https://nf-co.re logo
Join Slack
Powered by
Where is it I can find the logs for the full AWS t...
# help
d
Where is it I can find the logs for the full AWS tests?
p
Ask on #C09H6NYHR9T to be added to Seqrea Platform
d
I think I am already, I have seen run reports before but I can't find them now
p
Do you have a link?
d
No. The #C02FC6VFQG1 run fails (seems to be different errors) and I'd like to investigate and I know there are run reports somewhere at the seqera web site (I'm logged in) but I can't find them.
p
Failed after 5 hours on 
NFCORE_METATDENOVO:METATDENOVO:MEGAHIT_INTERLEAVED
Copy code
Error executing process > 'NFCORE_METATDENOVO:METATDENOVO:MEGAHIT_INTERLEAVED (megahit_assembly)'

Caused by:
  Missing output file(s) `megahit_out/megahit_assembly.contigs.fa.gz` expected by process `NFCORE_METATDENOVO:METATDENOVO:MEGAHIT_INTERLEAVED (megahit_assembly)`


Command executed:

  megahit \
      --12 ERR978615.processed.fastq.gz,ERR978616.processed.fastq.gz,ERR978614.processed.fastq.gz,ERR978612.processed.fastq.gz \
       \
      -t 1 \
      -m 214748364800 \
       \
      --out-prefix megahit_assembly

  pigz \
      --no-name \
      -p 1 \
       \
      megahit_out/*.fa \
      megahit_out/intermediate_contigs/*.fa

Command exit status:
  0

Command output:
  (empty)

Command error:
  2026-06-26 14:45:58 - MEGAHIT v1.2.9
  2026-06-26 14:45:59 - Using megahit_core with POPCNT and BMI2 support
  2026-06-26 14:45:59 - Convert reads to binary library
  2026-06-26 14:47:10 - b'INFO  sequence/io/sequence_lib.cpp  :   75 - Lib 0 (/fusion/s3/nf-core-awsmegatests/work/metatdenovo/work-4d0307aa7d34575aa7891a7b4996ffe19e774cd9/9f/467bd1fc700aad17bed2e84015d437/ERR978615.processed.fastq.gz): interleaved, 40525544 reads, 101 max length'
  2026-06-26 14:48:31 - b'INFO  sequence/io/sequence_lib.cpp  :   75 - Lib 1 (/fusion/s3/nf-core-awsmegatests/work/metatdenovo/work-4d0307aa7d34575aa7891a7b4996ffe19e774cd9/9f/467bd1fc700aad17bed2e84015d437/ERR978616.processed.fastq.gz): interleaved, 45305414 reads, 101 max length'
  2026-06-26 14:50:59 - b'INFO  sequence/io/sequence_lib.cpp  :   75 - Lib 2 (/fusion/s3/nf-core-awsmegatests/work/metatdenovo/work-4d0307aa7d34575aa7891a7b4996ffe19e774cd9/9f/467bd1fc700aad17bed2e84015d437/ERR978614.processed.fastq.gz): interleaved, 83969516 reads, 101 max length'
  2026-06-26 14:53:40 - b'INFO  sequence/io/sequence_lib.cpp  :   75 - Lib 3 (/fusion/s3/nf-core-awsmegatests/work/metatdenovo/work-4d0307aa7d34575aa7891a7b4996ffe19e774cd9/9f/467bd1fc700aad17bed2e84015d437/ERR978612.processed.fastq.gz): interleaved, 91205786 reads, 101 max length'
  2026-06-26 14:53:40 - b'INFO  utils/utils.h                 :  152 - Real: 461.8109\tuser: 129.5027\tsys: 36.2367\tmaxrss: 281384'
  2026-06-26 14:53:40 - k-max reset to: 119
  2026-06-26 14:53:40 - Start assembly. Number of CPU threads 1
  2026-06-26 14:53:40 - k list: 21,29,39,59,79,99,119
  2026-06-26 14:53:40 - Memory used: 214748364800
  2026-06-26 14:53:40 - Extract solid (k+1)-mers for k = 21
  2026-06-26 16:56:58 - Build graph for k = 21
  2026-06-26 17:03:01 - Assemble contigs from SdBG for k = 21
  2026-06-26 17:52:17 - Local assembly for k = 21
  2026-06-26 17:59:32 - Extract iterative edges from k = 21 to 29
  2026-06-26 18:20:10 - Build graph for k = 29
  2026-06-26 18:23:17 - Assemble contigs from SdBG for k = 29
  2026-06-26 18:42:27 - Local assembly for k = 29

Work dir:
  <s3://nf-core-awsmegatests/work/metatdenovo/work-4d0307aa7d34575aa7891a7b4996ffe19e774cd9/9f/467bd1fc700aad17bed2e84015d437>

Container:
  <http://wave.seqera.io/wt/f2e9c27936b7/biocontainers/mulled-v2-0f92c152b180c7cd39d9b0e6822f8c89ccb59c99:8ec213d21e5d03f9db54898a2baeaf8ec729b447-0|wave.seqera.io/wt/f2e9c27936b7/biocontainers/mulled-v2-0f92c152b180c7cd39d9b0e6822f8c89ccb59c99:8ec213d21e5d03f9db54898a2baeaf8ec729b447-0>

Tip: you can replicate the issue by changing to the process work dir and entering the command `bash .command.run`
Seqera AI thinks it's a spot-instance interruption
Most of the time we don't notice this, as we have Fusion enabled with snapshots, which is able to freeze the task in-flight and resume it again on a new instance like magic magic
However this task had 200GB memory allocated, so my guess is that Fusion didn't have time to finish transferring the huuuuge snapshot file
CleanShot 2026-06-27 at 01.21.58@2x.png
👍 1
2 Views
Open in Slack
PreviousNext
Powered by