-
Notifications
You must be signed in to change notification settings - Fork 314
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
Implement ChainRunner #1869
Implement ChainRunner #1869
Conversation
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
016c883
to
eb83409
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1869 +/- ##
==========================================
- Coverage 94.61% 94.61% -0.01%
==========================================
Files 459 459
Lines 43637 43639 +2
==========================================
+ Hits 41287 41288 +1
- Misses 2350 2351 +1
☔ View full report in Codecov by Sentry. |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
eb83409
to
193600f
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
193600f
to
2ebda85
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
2ebda85
to
ddc5fb3
Compare
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
ddc5fb3
to
8614372
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Differential Revision: D47484883
8614372
to
44b19aa
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Reviewed By: lena-kashtelyan Differential Revision: D47484883
44b19aa
to
64671e0
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Reviewed By: lena-kashtelyan Differential Revision: D47484883
64671e0
to
6aeca61
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
Summary: Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial. High-level logic is as follows: * `ChainRunner.run` kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata. * `ChainRunner.poll_trial_status` polls the current stage's runner's status. If this is `TrialStatus.COMPLETED` and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process. In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient). Reviewed By: lena-kashtelyan Differential Revision: D47484883
6aeca61
to
48fb7ea
Compare
This pull request was exported from Phabricator. Differential Revision: D47484883 |
This pull request has been merged in 2e71d92. |
Summary:
Implements ChainRunner, which takes List[ChainRunnerStage] and runs the stages in sequence for each trial.
High-level logic is as follows:
ChainRunner.run
kicks off the first ChainRunnerStage in the list and records that stage's name in the trial's run_metadata.ChainRunner.poll_trial_status
polls the current stage's runner's status. If this isTrialStatus.COMPLETED
and there are more stages left in the chain, ChainRunner kicks off the next stage in the chain, updating the run_metadata in the process.In the future this should be implemented such that this state management happens in the calling context (e.g., Scheduler, AxClient).
Differential Revision: D47484883