This is a staging environment. For live and up-to-date package information, visit swiftpackageindex.com.

The Swift Package Index logo.Swift Package Index

Track the adoption of Swift 6 strict concurrency checks for data race safety. How many packages are Ready for Swift 6?

Build Information

Failed to build XCTestStarterKit with Swift 6.0 for Linux.

Build Command

bash -c docker run --rm -v "checkouts-4606859-0":/host -w "$workDir" registry.gitlab.com/finestructure/spi-images:basic-6.0-latest swift build --triple x86_64-unknown-linux-gnu -Xswiftc -Xfrontend -Xswiftc -stats-output-dir -Xswiftc -Xfrontend -Xswiftc .stats -Xswiftc -strict-concurrency=complete 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 4.40.0
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/CypherPoet/XCTestStarterKit.git
Reference: main
Initialized empty Git repository in /host/spi-builder-workspace/.git/
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint: 	git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint: 	git branch -m <name>
From https://github.com/CypherPoet/XCTestStarterKit
 * branch            main       -> FETCH_HEAD
 * [new branch]      main       -> origin/main
HEAD is now at 2d9557c Rename LICENSE to LICENSE.md
Cloned https://github.com/CypherPoet/XCTestStarterKit.git
Revision (git rev-parse @):
2d9557c37ba61542c638bbc87dbbc814e0d5ffe4
SUCCESS checkout https://github.com/CypherPoet/XCTestStarterKit.git at main
========================================
Build
========================================
Selected platform:         linux
Swift version:             6.0
Building package at path:  $workDir
https://github.com/CypherPoet/XCTestStarterKit.git
Running build ...
bash -c docker run --rm -v "checkouts-4606859-0":/host -w "$workDir" registry.gitlab.com/finestructure/spi-images:basic-6.0-latest swift build --triple x86_64-unknown-linux-gnu -Xswiftc -Xfrontend -Xswiftc -stats-output-dir -Xswiftc -Xfrontend -Xswiftc .stats -Xswiftc -strict-concurrency=complete 2>&1
Building for debugging...
[0/2] Write sources
[1/2] Write swift-version-24593BA9C3E375BF.txt
error: emit-module command failed with exit code 1 (use -v to see invocation)
[3/6] Emitting module XCTestStarterKit
/host/spi-builder-workspace/Sources/XCTestStarterKit/Extensions/XCTestCase/XCTestCase+AwaitCompletionOfPublisher.swift:2:8: error: no such module 'Combine'
 1 | import Foundation
 2 | import Combine
   |        `- error: no such module 'Combine'
 3 | import XCTest
 4 |
[4/6] Compiling XCTestStarterKit XCTestCase+AssertResultCompletesWithError.swift
/host/spi-builder-workspace/Sources/XCTestStarterKit/Extensions/XCTestCase/XCTestCase+AwaitCompletionOfPublisher.swift:2:8: error: no such module 'Combine'
 1 | import Foundation
 2 | import Combine
   |        `- error: no such module 'Combine'
 3 | import XCTest
 4 |
[5/6] Compiling XCTestStarterKit XCTestCase+AssertExpressionThrowsError.swift
/host/spi-builder-workspace/Sources/XCTestStarterKit/Extensions/XCTestCase/XCTestCase+AwaitCompletionOfPublisher.swift:2:8: error: no such module 'Combine'
 1 | import Foundation
 2 | import Combine
   |        `- error: no such module 'Combine'
 3 | import XCTest
 4 |
[6/6] Compiling XCTestStarterKit XCTestCase+AwaitCompletionOfPublisher.swift
/host/spi-builder-workspace/Sources/XCTestStarterKit/Extensions/XCTestCase/XCTestCase+AwaitCompletionOfPublisher.swift:2:8: error: no such module 'Combine'
 1 | import Foundation
 2 | import Combine
   |        `- error: no such module 'Combine'
 3 | import XCTest
 4 |
BUILD FAILURE 6.0 linux
This is a staging environment. For live and up-to-date package information, visit swiftpackageindex.com.