The Swift Package Index logo.Swift Package Index

Build Information

Failed to build Runner, reference v2.1.5 (ba4b7d), with Swift 6.2 for Wasm on 9 Oct 2025 14:17:13 UTC.

Build Command

bash -c docker run --pull=always --rm -v "checkouts-4609320-0":/host -w "$PWD" -e JAVA_HOME="/root/.sdkman/candidates/java/current" -e SPI_BUILD="1" -e SPI_PROCESSING="1" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasip1 2>&1

Build Log

========================================
RunAll
========================================
Builder version: 4.68.0
Interrupt handler set up.
========================================
Checkout
========================================
Clone URL: https://github.com/elegantchaos/Runner.git
Reference: v2.1.5
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/elegantchaos/Runner
 * tag               v2.1.5     -> FETCH_HEAD
HEAD is now at ba4b7d5 Adopt queue-based DataBuffer.
Cloned https://github.com/elegantchaos/Runner.git
Revision (git rev-parse @):
ba4b7d5b995d33c82fc1aa51054202caf0aa7297
SUCCESS checkout https://github.com/elegantchaos/Runner.git at v2.1.5
========================================
Build
========================================
Selected platform:         wasm
Swift version:             6.2
Building package at path:  $PWD
https://github.com/elegantchaos/Runner.git
Running build ...
bash -c docker run --pull=always --rm -v "checkouts-4609320-0":/host -w "$PWD" -e JAVA_HOME="/root/.sdkman/candidates/java/current" -e SPI_BUILD="1" -e SPI_PROCESSING="1" registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest swift build --swift-sdk wasm32-unknown-wasip1 2>&1
wasm-6.2-latest: Pulling from finestructure/spi-images
Digest: sha256:f6b6b9bdb5d5605d727da337418fc455cd8a0394d3a815b70631008c48829755
Status: Image is up to date for registry.gitlab.com/finestructure/spi-images:wasm-6.2-latest
warning: multiple Swift SDKs match target triple `wasm32-unknown-wasip1` and host triple x86_64-unknown-linux-gnu, selected one at /root/.swiftpm/swift-sdks/swift-6.2-RELEASE_wasm.artifactbundle/swift-6.2-RELEASE_wasm/wasm32-unknown-wasip1/embedded-swift-sdk.json
Fetching https://github.com/elegantchaos/ChaosByteStreams
[1/129] Fetching chaosbytestreams
Fetched https://github.com/elegantchaos/ChaosByteStreams from cache (0.86s)
Computing version for https://github.com/elegantchaos/ChaosByteStreams
Computed https://github.com/elegantchaos/ChaosByteStreams at 1.0.7 (16.08s)
Creating working copy for https://github.com/elegantchaos/ChaosByteStreams
Working copy of https://github.com/elegantchaos/ChaosByteStreams resolved at 1.0.7
Building for debugging...
[0/3] Write sources
[2/3] Write swift-version-24593BA9C3E375BF.txt
error: emit-module command failed with exit code 1 (use -v to see invocation)
[4/5] Emitting module ChaosByteStreams
/host/spi-builder-workspace/.build/checkouts/ChaosByteStreams/Sources/ChaosByteStreams/Data+ByteStreams.swift:1:8: error: no such module 'Foundation'
 1 | import Foundation
   |        `- error: no such module 'Foundation'
 2 |
 3 | /// Byte stream extensions for data.
[5/5] Compiling ChaosByteStreams Data+ByteStreams.swift
/host/spi-builder-workspace/.build/checkouts/ChaosByteStreams/Sources/ChaosByteStreams/Data+ByteStreams.swift:1:8: error: no such module 'Foundation'
 1 | import Foundation
   |        `- error: no such module 'Foundation'
 2 |
 3 | /// Byte stream extensions for data.
BUILD FAILURE 6.2 wasm