test: enable owned emulator power-cycle checks under network guard - #70
Draft
BitHighlander wants to merge 1 commit into
Draft
test: enable owned emulator power-cycle checks under network guard#70BitHighlander wants to merge 1 commit into
BitHighlander wants to merge 1 commit into
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
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.
Storage migration tests launch their own emulator on dynamically allocated loopback UDP ports, which the authoritative network guard denied. Lease only that exact main/debug pair while the process runs and revoke it on halt or startup failure. Network policy tests verify allowed local UDP, denial of unrelated/remote endpoints, and revocation. The exact 7.15 storage suite now passes 14 tests with one documented inapplicable burned-version skip. Bitcoin-only execution exposed two existing full-variant assumptions, tracked separately; no firmware behavior changed.