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

Job status in web UI should better reflect actual status in engine #74

Closed
bertfrees opened this issue Mar 10, 2016 · 3 comments
Closed
Labels

Comments

@bertfrees
Copy link
Member

For example:

  • For jobs listed as "running" it should be checked whether they are actually still running. For instance if the engine was restarted in the middle of a job it's probably not running anymore when the engine comes back online. This can be very confusing. The job should probably say "Failed" or maybe "Cancelled" or something.
  • Related: When a job is deleted in the web UI it shouldn't be removed from the list until it is actually gone in the engine: Don't delete the webui job if the engine job is not deleted #62

Also related: #61

@josteinaj
Copy link
Member

The first issue where they have the state "running" permanently I believe to be an issue with the engine. I haven't looked into it for a while though.

@bertfrees
Copy link
Member Author

See daisy/pipeline-framework#105.

@josteinaj
Copy link
Member

I'm closing this one as all the issues mentioned have separate issues.

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

No branches or pull requests

2 participants