Ensure IRC update failure still lets TRC update + bug fix + UTs - #78
Merged
Conversation
birukyitbarek
approved these changes
Jul 22, 2026
birukyitbarek
approved these changes
Aug 24, 2026
Vivek Lingaiah (viveklingaiah)
approved these changes
Aug 24, 2026
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
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.
Problem/Overview:
In the case where both IRC and traditional run command (TRC) exist on a VM, and there is an update available, both IRC and TRC will update. Previously, if IRC failed to update, then TRC.Update() would error out before copying over the mrseq files, and thus causing a re-trigger of RC to run.
Additionally, in this case, IRC was failing to update if the extension was the test extension, as opposed to the prod extension.
This PR includes: