-
Notifications
You must be signed in to change notification settings - Fork 45
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
Missing results of tasks at the end of a run #1159
Comments
The message looks like some tasks from the master tasks are not returned for some reason. I will try to reproduce it. |
There are 6283 failed IDs, does not roughly match the number of empty files? |
I'm not sure. But I assume we can create a MWE to test it? I'll do it after dinner. |
Indeed, here is a MWE:
the outcome:
The problem is still with |
So basically |
Sorry let me reopen this ticket with an additional step in the MWE above, to demonstrate there are still some "holes" somewhere:
Notice here I did not use
i'm on current |
This is because there are two empty groups so you have two |
Yes I understand that ... this is another type of hole that we should take care of. |
This is the consequence of
|
So we are back to discussing #1132 ? |
I guess so because in any case collapsing |
I added this line to my workflow for now:
it helps. I will close this ticket and add more info at #1132. |
At the end of #1156, it seems my tasks are all re-evaluated but the pipeline stopped with an error message claiming about 6K tasks "cannot be found". The error message is attached:
failed_to_get_results.txt
Not sure what this is about. The status of these tasks are
missing
if you check on the cluster. One possibliyti is I currently added astop_if
like:and I do have a few thousands files empty. But it should be skipped before job submission? Other than that I'm not sure why things are missing, or what jobs exactly is it checking.
In any case the consequence is that the execution stopped, leaving behind a scary message of large number of missing tasks. There is no single failure reported though (all my R computations were done without an error at least according to SoS)
The text was updated successfully, but these errors were encountered: