Fix Firewall E2E Test under Windows Sandbox (with Windows Insider release) #586
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.
I suspect a recent update to the Windows Insider build has resulted in my Windows Sandbox producing the below MSI E2E test failures.
This is potentially a Windows OS bug (it was from a Windows Insider build), however it does show that it's possible in the Firewall API to have multiple rules which differ only in their Grouping.
So the testbench should consider different Grouping as making for a unique firewall rule.