We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
pipe(2)
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
WASI does not have pipe system call, and wasi-libc doesn't provide any stub for it. So WASI build started failing after #694.
pipe
/home/build-user/swift-testing/Sources/Testing/Support/FileHandle.swift:449:20: error: cannot find 'pipe' in scope 447 | } 448 | #else 449 | guard 0 == pipe(fds.baseAddress) else { | `- error: cannot find 'pipe' in scope 450 | throw CError(rawValue: swt_errno()) 451 | }
https://ci.swift.org/job/oss-swift-pr-test-crosscompile-wasm-ubuntu-20_04/1525/console
Conditionalize the use of pipe(2) by something like SWT_NO_PIPE in swift-testing side.
SWT_NO_PIPE
No response
swift --version ; uname -a
The text was updated successfully, but these errors were encountered:
Pipe
Disable pipes code on WASI.
58981a8
WASI does not support pipes. Resolves #698.
9693475
Disable pipes code on WASI. (#699)
324f6b8
WASI does not support pipes. Resolves #698. ### Checklist: - [x] Code and documentation should follow the style of the [Style Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md). - [x] If public symbols are renamed or modified, DocC references should be updated.
grynspan
Successfully merging a pull request may close this issue.
Description
WASI does not have
pipe
system call, and wasi-libc doesn't provide any stub for it. So WASI build started failing after #694.https://ci.swift.org/job/oss-swift-pr-test-crosscompile-wasm-ubuntu-20_04/1525/console
Expected behavior
Conditionalize the use of
pipe(2)
by something likeSWT_NO_PIPE
in swift-testing side.Actual behavior
No response
Steps to reproduce
No response
swift-testing version/commit hash
No response
Swift & OS version (output of
swift --version ; uname -a
)No response
The text was updated successfully, but these errors were encountered: