-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add detailed experiment status #663
Conversation
Note: this PR is based on #604 . The real amount of files changed is much smaller. Please don't review until this other PR is merged. |
43fc199
to
fd4da0b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TY @javiermtorres ! I added minor fixes to be applied before merging.
Blocking this just because I want to make sure the above are already covered by tests before merging, but if you can confirm this I am happy to approve it!
Co-authored-by: Davide Eynard <[email protected]> Signed-off-by: javiermtorres <[email protected]>
7f1f9ed
to
80c57e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TY @javiermtorres for implementing the new logic!
This looks good to me, I am happy to preapprove it. Re: impact on the current UI, there will be none as this service is hit only by the new endpoint
What's changing
Adds detailed experiment status depending on the component job status.
Closes #571
How to test it
Integration tests are supplied with the change. Manually, the status can be retrieved and checked while the component jobs are cycling through their RUNNING and SUCCEEDED/FAILED status.
Additional notes for reviewers
N/A
I already...
/docs
)