Repository navigation
test: wait for container controls in ARM release regression - #40
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.
Make the log-stream cancellation regression wait for rendered inspection controls. The ARM release build exposed that observing label requests did not prove the inspection had finished, so the test could click a Logs tab that was not mounted yet.
The fixture now deliberately delays inspection, asserts the tab is absent while loading, resolves inspection, and waits for the actual Logs control before testing cancellation. All cancellation assertions remain; no test is skipped and no timeout or CI check is relaxed.
Validation: clean lint and TypeScript checks, all 27 UI tests, and the production build pass. The failed v0.9.1 tag is preserved; the corrected source will be released as v0.9.2 after exact-head CI.