Update to use scenario=flight in make_timeline.py#94
Merged
Conversation
jeanconn
force-pushed
the
kadi-scenario
branch
from
d7cf093 to
f113584
Compare
jeanconn
changed the title
Contributor
Author
|
Given the scope, I'm wondering if we can skip end-to-end functional testing on this one and just verify by inspection the change is formatted correctly and get the functional testing as part of #95 . |
Contributor
Author
|
This has now been functionally tested in #95 |
Contributor
Author
|
Technically, I think this still needs approval before I should cut a release and to the FSDS. |
Update paths for MTA radiation reorg
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Update to use scenario=flight for make_timeline.py.
Replan central runs on HEAD and always has access to up-to-date commands in /proj/sot/ska, so there's no reason to do web queries (that frequently fail and toss warnings into the arc logs).
Interface impacts
Functional testing
No functional testing.