Repository navigation
Match the controlled Windows setup-error fixture diagnostic (#907) - #918
Merged
Merged
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.
The same-ZIP packaged Windows test reached a real terminal failure UI, but its expected error was wrong: the service override is outside the bundled BUILD.json/runtime directory, so launchPaths reports its deterministic path-mapping error before native spawn. Assert that exact setup error, retain the error phase, seven-second persistence and explicit Retry checks.
Run 41788251314 remains failed. It proved cold startup/main UI and recorded both UI processes exiting 0, the resident hub stopped and the disposable account removed. Retest only the identical 0.14.1 ZIP (SHA256 0d45d809325d7dd5067273e60c9b462e478f5aae3109fc30cb8264aa6a042137). No packaged source, rebuild, relink or emitter change.