Add ability to run scheduling within delay_info_main.
#3198
+75
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![copybara-service[bot]](https://avatars.githubusercontent.com/in/44061?s=80&v=4){kind=small}
This change allows `delay_info_main` to generate a pipeline schedule on the fly using scheduling options flags (e.g., `--pipeline_stages`, or even `--scheduling_options_proto` providing all of the arguments at once) instead of requiring a pre-existing schedule file via `--schedule_path`. PiperOrigin-RevId: 819903820
copybara-service
bot
force-pushed
the
test_819903820
branch
from
dbdf85e to
b504372
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add ability to run scheduling within
delay_info_main.This change allows
delay_info_mainto generate a pipeline schedule on the fly using scheduling options flags (e.g.,--pipeline_stages, or even--scheduling_options_protoproviding all of the arguments at once) instead of requiring a pre-existing schedule file via--schedule_path.