Reproduce Swift collector loss after an XCUITest runner restart - #65
Open
pda wants to merge 1 commit into
Open
Conversation
![buildsworth-bk-app[bot]](https://avatars.githubusercontent.com/in/3010600?s=60&v=4){kind=small}
Extend the green XCUITest fixture with a crash-once marker persisted by the target app. Two tests finish before the UI test runner kills itself; Xcode then replaces the runner and continues the remaining tests. Capture collector debug output and compare its unique uploaded test names with the completed xcresult. The local reproduction retains all five tests in xcresult but records only the two tests run after replacement. Keep an intentional post-restart assertion failure to prove execution tags, source location, and expanded backtrace remain available on delivered traces. The pipeline step is soft-failed because this branch is intentionally a failing regression fixture until the collector gains durable delivery. Amp-Thread-ID: https://ampcode.com/threads/T-01a036f0-4e44-73ab-a085-68af2e00b5cb Co-authored-by: Amp <amp@ampcode.com>
pda
force-pushed
the
reproduce-swift-xcuitest-runner-loss
branch
from
August 25, 2026 07:20
df12e25 to
92b7a64
Compare
This was referenced Aug 25, 2026
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
1 participant
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.
Why
test-collector-swiftbuffers completed tests in the XCTest runner and flushes only when the bundle finishes. If Xcode replaces that process mid-suite, completed executions disappear even though.xcresultremains complete.This PR is intentionally stacked on #64 so the normal green XCUITest integration can be reviewed and merged separately.
What
.xcresultwith unique test names in the collector's upload logObserved result
On Xcode 26.5,
.xcresultretained all 5 tests while the collector recorded only the 2 tests completed by the replacement runner. The surviving failure retained its native location, expanded backtrace, and execution tag. The verifier fails on the 5-vs-2 mismatch as intended.Rollback
Revert this PR to return #64's green XCUITest example; no persistent data or migrations are involved.
Related