Verify Swift OTLP delivery across XCUITest runner replacement - #68
Draft
pda wants to merge 6 commits into
Draft
Conversation
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>
Run the XCTest example against the OTLP-only collector branch and use the bktec relay for hosted macOS XCUITest. Verify that every completed execution reaches the relay across XCTest runner replacement while documenting the unavoidable active-test SIGKILL gap. Amp-Thread-ID: https://ampcode.com/threads/T-01a037c7-e3e7-70e4-b18f-a43cec542d56 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-01a037c7-e3e7-70e4-b18f-a43cec542d56 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-01a037c7-e3e7-70e4-b18f-a43cec542d56 Co-authored-by: Amp <amp@ampcode.com>
Upgrade the Tests plugin so it can install the bktec relay release candidate, and resolve both Swift examples with Swift 6.0-compatible transitive versions. Amp-Thread-ID: https://ampcode.com/threads/T-01a037c7-e3e7-70e4-b18f-a43cec542d56 Co-authored-by: Amp <amp@ampcode.com>
Lower the Linux example manifest to Swift tools 5.10 and pin the transitive collector graph to versions that compile with Swift 5.10/Xcode 15.4. Teach the XCUITest result verifier to read both the modern test-results summary and the legacy XCResult action schema. This keeps the hosted macOS check strict about all five records, including the deliberately killed runner, without requiring a newer xcresulttool. Amp-Thread-ID: https://ampcode.com/threads/T-01a037c7-e3e7-70e4-b18f-a43cec542d56 Co-authored-by: Amp <amp@ampcode.com>
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
The XCUITest reproduction in #65 shows that the proprietary Swift collector uploader can lose completed executions when Xcode replaces the test runner mid-suite. buildkite/bktest#12 replaces that uploader with test root spans sent over OTLP, so the examples need to exercise both direct export and the hosted macOS relay path before that change lands.
What
buildkite/bktest#12bktecOTLP relay.xcresultcontains all five test records while all four completed XCTest callbacks are accepted over OTLPSIGKILLed test cannot emit a span because XCTest never delivers its completion callbackRelated reproduction: #65