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
Error in rule bundle:
message: SLURM-job '665356' failed, SLURM status is: 'FAILED'. For further error details see the cluster/cloud log and the log files of the involved rule(s).
jobid: 1
input: a.txt (retrieve from storage), b.txt (retrieve from storage), c.txt (retrieve from storage)
output: data.tar.gz (send to storage)
log: /gpfs/fs1/home/meesters/snakemake-irods/.snakemake/slurm_logs/rule_bundle/665356.log (check log file(s) for error details)
shell:
tir czf /dev/shm/\meesters/fs/data.tar.gz /dev/shm/\meesters/fs/a.txt /dev/shm/\meesters/fs/b.txt /dev/shm/\meesters/fs/c.txt
(one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
external_jobid: 665356
Apparently, the SLURM job considers local-storage-prefix to be the one it should be using, rather than remote-job-local-storage-prefix.
Also, the env variables need to be escaped to get that far. Otherwise, the foo jobs abort with touch /dev/shm/meesters/fs/c.txt, where fs is introduced in the path and that is simply not created, hence the abort.
I wonder, does the executor need an additional flag to consider the remote path?
The text was updated successfully, but these errors were encountered:
This mini-PR tries to emphasize the need to escape remote env variables.
It addresses #28 . Whether it actually does the trick remains to be seen
- when my cluster is accessible again.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Refined explanatory text to improve clarity.
- Updated configuration examples to ensure proper escaping of
environment variables for accurate guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Hi,
given this mini workflow:
which should bundle the output with
tar
and is intentionally broken and this config:the
bundle
rule fails with:Apparently, the SLURM job considers
local-storage-prefix
to be the one it should be using, rather thanremote-job-local-storage-prefix
.Also, the env variables need to be escaped to get that far. Otherwise, the
foo
jobs abort withtouch /dev/shm/meesters/fs/c.txt
, wherefs
is introduced in the path and that is simply not created, hence the abort.I wonder, does the executor need an additional flag to consider the remote path?
The text was updated successfully, but these errors were encountered: