engine: don't run empty LiveUpdateInfos thru buildAndDeploy (eliminates log spam when LU-ing only one of multiple images)#2018
Merged
Conversation
…es log spam when LU-ing only one of multiple images
nicks
approved these changes
Aug 8, 2019
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.
Previously, LiveUpdating a manifest with two images, changing a file that synced to only one of the images, would get:
(the second empty log line being from an empty LiveUpdInfo that we ran thru
buildAndDeploy)this PR fixes the typo in []liveUpdInfos initialization that caused us to run empties thru the deploy process