Skip to content

ci: run ClientDisconnectTests again in the Release SwiftLM job - #116

Merged
solderzzc merged 1 commit into
mainfrom
ci/unskip-clientdisconnect
Nov 4, 2026
Merged

solderzzc merged 1 commit into
mainfrom
ci/unskip-clientdisconnect

Conversation

@solderzzc

Copy link
Copy Markdown
Member

Removes --skip ClientDisconnectTests from the swiftlm job in .github/workflows/ci.yml; --disable-swift-testing stays.

Why

ClientDisconnectTests aborted the XCTest process in Release on Swift 6.2.4 (Xcode 26.3). Root cause: Task.sleep(for:) in the SwiftLM test bundle (not SwiftLM's cancellation code). SharpAI/SwiftLM#256, merged as 69bc71c, switched the test sleeps to Task.sleep(nanoseconds:). The job checks out SwiftLM main, so it already has that fix.

Evidence

  • Locally on Swift 6.2.4, Release, SwiftLM at Add Gemma 4 video tower support ml-explore/mlx-swift-lm#256's head: ClientDisconnectTests 7 tests 0 failures, whole SwiftLMTests bundle 464 tests 0 failures (EXIT=0).
  • This PR's own CI is the real check: the CI SwiftLM job must run the 7 tests and pass. Merge only if it is green; a CANCELLED check is not a pass.

Not verified

  • Whether the 7 server-side Task.sleep(for:) calls in Server.swift behave on 6.2.4 outside tests (not changed).
  • That CI (Xcode 26.3 on the hosted runner) behaves like the local Xcode 26.3 install.

🤖 Generated with Claude Code

SwiftLM#256 (69bc71c) replaced Task.sleep(for:) in its tests. On Swift 6.2.4 in Release
that call aborts the XCTest process ('freed pointer was not the last allocation'); the
suite now passes there (7 tests, 464 in the whole bundle, checked locally).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@solderzzc
solderzzc merged commit e5b737b into main Nov 4, 2026
2 checks passed
@solderzzc
solderzzc deleted the ci/unskip-clientdisconnect branch November 4, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant