Repository navigation
Conversation
CircleCI retired configuration version 2 at the end of September, so every pipeline since then has errored before running a single step. Declaring version 2.1 restores the builds. The image moves to Xcode 27 to match the browser build and local development.
xcbeautify hides xcodebuild's own progress messages, so when the test step went silent for ten minutes after the last bundle finished there was nothing to say why. Tee the raw output to files and store them.
With every test passing, xcodebuild still spent 600 seconds trying to collect simulator diagnostics and timed out, and CircleCI's ten-minute no-output limit killed the step one second earlier. The raw log from the previous run shows it. Diagnostics are not useful on CI anyway; the junit report and the raw log are what we read.
A test host crashed with an index out of range on CI but not locally, and without the crash report there is no stack to read.
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
2 participants
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.
CircleCI retired configuration version 2 at the end of September. This repo's
.circleci/config.ymlnever declaredversion: 2.1, so every pipeline since Sept 30 errored at config validation before running a step:That includes the pipelines for the 3.14.9 merge into dev (#504) and for every branch pushed since. LoopKit's config already declares 2.1, which is why its builds kept running.
Changes:
declare
version: 2.1and drop the obsoleteworkflows: version: 2keybuild with the Xcode 27.0 image, matching the browser build workflows and current development
bump LoopKit to include Adopt the scene lifecycle in the LoopKit Example app LoopKit#632, which adopts the scene lifecycle in the LoopKit Example test host; without it the iOS 27 SDK traps that app at launch and LoopKitHostedTests never runs
keep the raw xcodebuild logs as artifacts, since xcbeautify hides xcodebuild's own messages
pass
-collect-test-diagnostics never: with every test passing, xcodebuild still spent 600 seconds failing to collect simulator diagnostics, and CircleCI's ten-minute no-output limit killed the step one second before it would have exited (builds 1223 to 1225)keep simulator crash reports as artifacts, for the intermittent host crash seen in build 1228 (being hardened in Fail hosted store tests on a short result instead of crashing the host LoopKit#633)
Status (build 1229): green. All eleven test bundles pass and the job completes in 4 minutes.