-
Notifications
You must be signed in to change notification settings - Fork 94
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
sim mode: traceback if execution retries and submission retrys unset #5935
Comments
7 tasks
I'm putting this off until the merger of #5721 changing the way sim mode works almost entirely. |
Sounds like this can go back to 8.4 then... |
Closed by #5721? |
I think probably for master, but not for 8.2.x. Needs double checking on both anyway. |
Oh looks like #5927 was to fix this on 8.2.x, but was closed? |
So I think that in the end my decision (with Oliver's approval) was as follows:
Therefore
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
You can get traceback when simulating execution retries if you haven't set submission retries.
How to replicate
Cause
The setting
submission retry delay
has no default. This means that inTaskJobManager.set_retry_timers
the following code will fail unless the user has setsubmission retry delay
:A possible second bug
I have found that after fixing this bug there is something wrong with the task_events_mgr, causing an endless loop of new job submissions:
Other questions
Why does this only affect simulation mode?
The text was updated successfully, but these errors were encountered: