Cache hosted builds and fix CI-discovered window and timing issues - #94
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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 hosted CI run now finishes its full Swift suite in about 40 seconds, but exposed delayed editor presentation that could reopen a closed window and imprecise media-duration reads. Cancel queued editor activation on close and superseded requests, request precise AVFoundation duration, and retain the duration and Dock assertions with a bounded wait for window state. Add a regression for closing while activation is pending.
Cache Swift dependencies and compiled debug/release products and Rust dependency/target products with toolchain, dependency, and source hashes. Explicit cache paths exclude Fastlane signing material and credentials. Cache hits never skip unit tests; owner merges remain the only test trigger and gate TestFlight.
Validation: 27 focused media/window tests passed; strict SwiftLint, actionlint, and workflow-policy tests passed. All 1,080 existing tests completed in the prior hosted run; the next run verifies these fixes and primes the build caches.