-
Notifications
You must be signed in to change notification settings - Fork 16
Ashishonce/multiplepruns #18
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
base: master
Are you sure you want to change the base?
Conversation
| print(f"::set-output name=run_metrics::{run_metrics}") | ||
| print(f"::set-output name=run_metrics_markdown::{run_metrics_markdown}") | ||
| submittedRuns_for_wait.remove(run) | ||
| time.sleep(10) # wait for 10 seconds to check again. |
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.
this wait time is point of check, do we wait for 10 seconds before checking status again?
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.
Given runs can be quite long, this seems reasonable. @marvinbuss thoughts?
marvinbuss
left a comment
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.
Before merging this:
- Add integration tests
- Describe features in Readme
will work on this PR once integration tests in other PR are checked in , will merge with that and update this PR |
Yes, let's focus on integration test and the other missing pieces for the next 2 weeks. |
this PR supports multiple runs, but with for loop instead of multiprocessing.
this has drawback over multiprocessing as it has a deterministic delay when multiple runs might be submitted.