Originally reported by @ashildv
Check Documentation
I have checked the following places for your error:
Description of the bug
If MultiQC crashes for whatever reason (other than 143/137), we have set it to be ignored rather than retry. This is a bit too blunt, as it means other cases when it crashes (e.g. walltime) it doesn't complete.
In particular when you have large datasets, hitting walltime is possible. We should remove the 'ignore' directive to start picking up valid kill exit codes and improve the retry system.
Steps to reproduce
Steps to reproduce the behaviour:
- Command line:
nextflow run ...
- See error: Please provide your error message
Expected behaviour
Log files
Have you provided the following extra information/files:
System
- Hardware:
- Executor:
- OS:
- Version
Nextflow Installation
Container engine
- Engine:
- version:
- Image tag:
Additional context
Originally reported by @ashildv
Check Documentation
I have checked the following places for your error:
- nf-core/eager FAQ/troubleshooting can be found here
Description of the bug
If MultiQC crashes for whatever reason (other than 143/137), we have set it to be ignored rather than retry. This is a bit too blunt, as it means other cases when it crashes (e.g. walltime) it doesn't complete.
In particular when you have large datasets, hitting walltime is possible. We should remove the 'ignore' directive to start picking up valid kill exit codes and improve the retry system.
Steps to reproduce
Steps to reproduce the behaviour:
nextflow run ...Expected behaviour
Log files
Have you provided the following extra information/files:
.nextflow.logfileSystem
Nextflow Installation
Container engine
Additional context