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

status reports NOT STARTED when jobs have been canceled befire running #212

Open
chuckatkins opened this issue Sep 29, 2020 · 1 comment

Comments

@chuckatkins
Copy link

Related to #205

After jobs are submitted but before they run then cheetah reports the status as "NOT STARTED". If the job is then canceled before starting then cheetah continues to report "NOT STARTED" and never reaches the "DONE" state.

@mw70
Copy link
Collaborator

mw70 commented Sep 29, 2020

Could you clarify? Are you talking about the status of the cheetah process, or the status of one of the runs/experiments inside the sweep group that cheetah created?
If it's the experiment, DONE doesn't seem to be the correct status for what you're reporting here. You defined an experiment in the sweep group, and then you canceled the execution of that particular experiment at some time. Since Cheetah offers the chance to rerun sweep groups to complete a campaign if you ran out of time, etc., marking a not-yet-run instance as DONE when it just hasn't run yet would cause problems.

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

No branches or pull requests

2 participants