-
Notifications
You must be signed in to change notification settings - Fork 0
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
Skip mode deconflict #70
Skip mode deconflict #70
Conversation
`json.dumps()`/`json.loads()` are relatively slow (~1us). But these functions are likely to be called many times with `flow={1}`.
…tasks in the given flow(s)
- Update data store with changed prereqs - Don't un-queue downstream task if: - the task is already preparing - the task exists in flows other than that being removed - the task's prereqs are still satisfied overall - Remove the downstream task from the pool if it no longer has any satisfied prerequisite tasks
This will allow it to call the method to kill submitted/running tasks
Plus ensure traceback for internal errors when cleaning gets logged in verbose mode
for p_name in set(platform_names) - set(JOBLESS_MODES): | ||
for p_name in set(platform_names): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The jobless logic here is not needed with my change to deep copy the localhost platform above
# Map jobless modes to localhost. | ||
ret.setdefault('localhost', []).extend( | ||
{'name': mode} for mode in JOBLESS_MODES | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto
to_kill.append(itask) | ||
if jobless: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note jobless
is really is_sim_mode
, see (above):
Line 1062 in b31f4ff
jobless = self.get_run_mode() == RunMode.SIMULATION |
This doesn't matter because you can't kill a skip mode task as it goes straight from waiting to succeeded
No description provided.