Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.10] Fix test runner build on WASI #7351

Conversation

kateinoigakukun
Copy link
Member

🍒 #7341

  • Explanation: swift build --build-tests fails on WASI after the experimental summary output, which is introduced in 5.10. This affects not only experimental-summary mode but also the default output mode.
  • Scope: Test build targeting WebAssembly
  • Risk: Low, only affects to WebAssembly targets
  • Testing: Integration test with WebAssembly Swift SDK on CI is infeasible, so I manually tested. We can ensure there is no breakage on other platforms on CI.
  • Reviewer: @MaxDesiatov
  • Main branch PR: Fix test runner build on WASI #7341

The test runner build was failing on WASI after the introduction of the
experimental summary output.

This PR fixes several minor issues to pass `--build-tests` build on
WASI:

* Missing `WASILibc` import
* The use of `flock` which is not available on WASI.
* Signature incompatibility of `XCTMain` on WASI.

`swift build --build-tests --triple wasm32-unknown-wasi` will pass when
compiler supports the target.
@kateinoigakukun kateinoigakukun added swift 5.10 This PR targets the 5.10 branch bug swift test Changes impacting `swift test` tool labels Feb 20, 2024
@kateinoigakukun
Copy link
Member Author

Can we include this fix in the next point release?

@MaxDesiatov
Copy link
Contributor

@swift-ci test

@MaxDesiatov MaxDesiatov merged commit 0ec3473 into swiftlang:release/5.10 Apr 3, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug swift test Changes impacting `swift test` tool swift 5.10 This PR targets the 5.10 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants