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

Skip should be the default behavior for shepherd if data already exist from a previous run #96

Open
glpuga opened this issue Aug 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@glpuga
Copy link
Collaborator

glpuga commented Aug 16, 2024

Feature description

Given how long and costly benchmarking runs are, and how potentially costly a mistake is to start the benchmark again withouth having edited the robot script to skip test cases already run and/or addding --skip-all in the right place in the shebang while debugging report generation, skipping the execution of a test case should be the default policy whenever output data from a previous run already exists.

Only the user should decide when to go nuclear on previous data.

Implementation considerations

If the output folder for a given test case already exist, log a warning, skip, and move on to the next.

@glpuga glpuga added the enhancement New feature or request label Aug 16, 2024
@glpuga glpuga changed the title --skip shiuld be the default behavior for shephers if data already exist from a previous run --skip should be the default behavior for shepherd if data already exist from a previous run Aug 16, 2024
@glpuga glpuga changed the title --skip should be the default behavior for shepherd if data already exist from a previous run Skip should be the default behavior for shepherd if data already exist from a previous run Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant