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
On failed mutation runs the mutator reverts to a single job (-j1) to retry the mutation run in case the failure is a concurrency issue. If THAT run fails it moves on.
If you rerun all mutations, the failed mutation runs try again, but they do so IMMEDIATELY with -j1 instead of retrying with more cores.
IMO the first time in a run that filed mutations are re-tried they should retry without the job parameter. The current workaround is to just delete the log file, which will start the mutation attempt over.
The text was updated successfully, but these errors were encountered:
On failed mutation runs the mutator reverts to a single job (-j1) to retry the mutation run in case the failure is a concurrency issue. If THAT run fails it moves on.
If you rerun all mutations, the failed mutation runs try again, but they do so IMMEDIATELY with
-j1
instead of retrying with more cores.IMO the first time in a run that filed mutations are re-tried they should retry without the job parameter. The current workaround is to just delete the log file, which will start the mutation attempt over.
The text was updated successfully, but these errors were encountered: