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

Failures should not be checkpointed #239

Closed
yadudoc opened this Issue Apr 26, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@yadudoc
Copy link
Member

yadudoc commented Apr 26, 2018

Current behavior caches and checkpoints failures. While we may reasonably expect to see failures repeat with apps where none of the inputs, code, or execution site within a single run, we should not assume the same for a re-run of the same workflow.

For eg, parsl does not completely account for :

  • transient behavior on remote sites/nodes
  • changes in remote env w.r.t packages
  • external scripts and data

I wanted to capture the rationale for the change in checkpointing behavior, since this was discussed in the comments for PR #237

@yadudoc yadudoc self-assigned this Apr 26, 2018

@yadudoc yadudoc added the enhancement label Apr 26, 2018

@yadudoc yadudoc added this to the Parsl-0.6.0 milestone Apr 26, 2018

yadudoc added a commit that referenced this issue May 1, 2018

yadudoc added a commit that referenced this issue May 1, 2018

@yadudoc yadudoc closed this Jun 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.