Skip to content
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

Running steps after early step interruption for memory usage #12209

Open
vlimant opened this issue Dec 17, 2024 · 0 comments
Open

Running steps after early step interruption for memory usage #12209

vlimant opened this issue Dec 17, 2024 · 0 comments

Comments

@vlimant
Copy link
Contributor

vlimant commented Dec 17, 2024

Apologies if this is already addressed somewhere else, and/or if not relevant.
As part of looking into a memory issue in RunIII2024Summer24DRPremix, I stumbled on the fact that in a stepchain setup, if one of the early step is interrupted by the memory watch-guard, the rest of the steps are ran regardless, and to my knowledge, since the job is marked as failed, any of the output will be discarded anyways.

Would it be better to stop the job at the step that was interrupted and not waste the cpu running things that will be thrown away ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant