-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snakemake jobs failing due to missing output files which do exist #123
Comments
wilfried ran into this issue too. snakemake rules succeeded but the overall slurm job failed. |
@kelly-sovacool ... can you point me to the output folder.. I am looking for the |
Wilfried's is here: jobby short file |
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@kopardev charlie writes the jobby files in |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Getting back to the retries / file latency issue: Here's another output dir where I only ran charlie once and did not manually resubmit it:
It looks like it is correctly resubmitting failed jobs with But rules seem to be failing due to missing output files on the first attempt even though they do exist. star_circrnafinderError message for attempt 1:
Error message for attempt 2:
It completed successfully on the 3rd attempt:
merge_alignment_statsError message for attempt 1:
Error message for attempt 2:
It completed successfully on the 3rd attempt.
create_hq_bamsAll of these jobs failed due to an import error which will be resolved by upgrading the base container to v7 (#125). This is unrelated the current issue.
|
--retries
is set to 2
|
I hesitate to go too high because that will needlessly delay the overall pipeline run completion. Should we reach out to biowulf staff about this?
I thought this was true, until we encountered #127 |
@kelly-sovacool is there a good root-cause for this yet? Else, we move this to Backlog with latency set to 300 and reaching out to Biowulf staff. |
so far I have not encountered this error recently, even with the original |
@kopardev found jobs will sometimes fail spontaneously and work on the re-run. It seems to be a file latency issue?
The text was updated successfully, but these errors were encountered: