Description of the bug
Linking files through metadata issues error in seqera platform
Also, rerunning becomes impossible as fasta and fai seem to be required to run the platform. This is not a problem for normal runs as igenomes reads the samples. Find a solution for full tests.
Command used and terminal output
Relevant files
No response
System information
`The exit status of the task that caused the workflow execution to fail was: 1
The failure reason of the task that caused the workflow execution to fail was: 7:34AM INF [seqera-fusion] setting up AWS Batch spot instance monitoring provider=aws-batch 7:34AM INF [seqera-fusion] instance metadata ami-id=ami-0acc5dd6b31082def instance-id=i-0ee43b2683972fbc2 instance-type=c6id.8xlarge 7:34AM INF [seqera-fusion] sta
Error executing process > 'NFCORE_VARIANTBENCHMARKING:VARIANTBENCHMARKING:REPORT_BENCHMARK_STATISTICS:DATAVZRD (rtgtools)'
Caused by:
Essential container in task exited
Command executed:
mkdir rtgtools
datavzrd
rtgtools.datavzrd.yaml
--output rtgtools \
Command exit status:
1
Command output:
(empty)
Command error:
7:34AM INF [seqera-fusion] setting up AWS Batch spot instance monitoring provider=aws-batch
7:34AM INF [seqera-fusion] instance metadata ami-id=ami-0acc5dd6b31082def instance-id=i-0ee43b2683972fbc2 instance-type=c6id.8xlarge
7:34AM INF [seqera-fusion] starting incremental snapshot timer interval=300000
Error: Failed to read dataset from path /nf-core-awsmegatests/work/variantbenchmarking/work-dev/a0/b435c27a2f834d76fec388131f0d3a/rtgtools.summary.csv
Caused by:
0: IO error: No such file or directory (os error 2)
1: No such file or directory (os error 2)
FUSION_GPU_USED=false
Fusion Info:
clone_namespace: false
kernel_version: 6.1
disk_cache_size: 1768Gb
max_open_files: 1048576
fusion_version: 2.4.21-a2fba53
Work dir:
s3://nf-core-awsmegatests/work/variantbenchmarking/work-dev/86/b696f384369b61be7c68eeec343c78
Container:
wave.seqera.io/wt/e0e4dc8c9f2b/library/datavzrd:2.63.3--b2276ffa6612b97f
Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named `.command.sh``
Description of the bug
Linking files through metadata issues error in seqera platform
Also, rerunning becomes impossible as fasta and fai seem to be required to run the platform. This is not a problem for normal runs as igenomes reads the samples. Find a solution for full tests.
Command used and terminal output
Relevant files
No response
System information
`The exit status of the task that caused the workflow execution to fail was: 1
The failure reason of the task that caused the workflow execution to fail was: 7:34AM INF [seqera-fusion] setting up AWS Batch spot instance monitoring provider=aws-batch 7:34AM INF [seqera-fusion] instance metadata ami-id=ami-0acc5dd6b31082def instance-id=i-0ee43b2683972fbc2 instance-type=c6id.8xlarge 7:34AM INF [seqera-fusion] sta
Error executing process > 'NFCORE_VARIANTBENCHMARKING:VARIANTBENCHMARKING:REPORT_BENCHMARK_STATISTICS:DATAVZRD (rtgtools)'
Caused by:
Essential container in task exited
Command executed:
mkdir rtgtools
datavzrd
rtgtools.datavzrd.yaml
--output rtgtools \
Command exit status:
1
Command output:
(empty)
Command error:
7:34AM INF [seqera-fusion] setting up AWS Batch spot instance monitoring provider=aws-batch
7:34AM INF [seqera-fusion] instance metadata ami-id=ami-0acc5dd6b31082def instance-id=i-0ee43b2683972fbc2 instance-type=c6id.8xlarge
7:34AM INF [seqera-fusion] starting incremental snapshot timer interval=300000
Error: Failed to read dataset from path /nf-core-awsmegatests/work/variantbenchmarking/work-dev/a0/b435c27a2f834d76fec388131f0d3a/rtgtools.summary.csv
Caused by:
0: IO error: No such file or directory (os error 2)
1: No such file or directory (os error 2)
FUSION_GPU_USED=false
Fusion Info:
clone_namespace: false
kernel_version: 6.1
disk_cache_size: 1768Gb
max_open_files: 1048576
fusion_version: 2.4.21-a2fba53
Work dir:
s3://nf-core-awsmegatests/work/variantbenchmarking/work-dev/86/b696f384369b61be7c68eeec343c78
Container:
wave.seqera.io/wt/e0e4dc8c9f2b/library/datavzrd:2.63.3--b2276ffa6612b97f
Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named `.command.sh``