-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix test runner build on WASI #7341
Fix test runner build on WASI #7341
Conversation
The test runner build was failing on WASI due to: * Missing `WASILibc` import * The use of `flock` and `open` which are not available on WASI. * Signature incompatibility of `XCTMain` on WASI.
@swift-ci Please smoke test |
@bnbarham actually there are more tests here I forgot about, but surfaced in this PR. |
@MaxDesiatov What do you mean "tests" here? The test runner can be built on any developer's machine not limited to our CI |
Ah, ok, sorry about the confusion. This is about |
Ensuring that the runner can be built for WASI requires actual Swift SDK, so i think we don't have good way to have a regression test in this repository unfortunately 😢 But we can have a validation test on our SwiftWasm build pipeline just in case. |
@swift-ci test |
@swift-ci test windows |
1 similar comment
@swift-ci test windows |
@swift-ci test windows |
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.
🍒 #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**: #7341
### Motivation: The test runner build was failing on WASI after the introduction of the experimental summary output. ### Modifications: 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. ### Result: `swift build --build-tests --triple wasm32-unknown-wasi` will pass when compiler supports the target.
### Motivation: The test runner build was failing on WASI after the introduction of the experimental summary output. ### Modifications: 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. ### Result: `swift build --build-tests --triple wasm32-unknown-wasi` will pass when compiler supports the target.
Motivation:
The test runner build was failing on WASI after the introduction of the experimental summary output.
Modifications:
This PR fixes several minor issues to pass
--build-tests
build on WASI:WASILibc
importflock
which is not available on WASI.XCTMain
on WASI.Result:
swift build --build-tests --triple wasm32-unknown-wasi
will pass when compiler supports the target