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.

Sign up for GitHub

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

Jump to bottom

Bring in cached executor #161

Open

vijayvammi opened this issue Nov 15, 2024 · 0 comments

Collaborator

vijayvammi commented Nov 15, 2024 •

edited

Loading

The cached executor or the iterative executor lets you gradually improve a previous run.

Any success step that is part of the run is skipped and moved to the next one.

Open question of nested steps.
Demands that the step names should be unique, which might have been enforced in the recent releases.

This is different to the retry executor which starts at the failure of the step.

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