Skip to content

chore: correct dir name #1

chore: correct dir name

chore: correct dir name #1

Triggered via push August 26, 2024 13:02
Status Failure
Total duration 1m 58s
Artifacts

build.yml

on: push
Matrix: build-wasm
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 1 warning
build-wasm (ubuntu-22.04)
file not found for module `tcp`
build-wasm (ubuntu-22.04)
file not found for module `udp`
build-wasm (ubuntu-22.04)
the name `tcp` is defined multiple times
build-wasm (ubuntu-22.04)
unresolved imports `crate::sys::tcp::bind`, `crate::sys::tcp::listen`, `crate::sys::tcp::new_for_addr`
build-wasm (ubuntu-22.04)
unresolved imports `crate::sys::tcp::connect`, `crate::sys::tcp::new_for_addr`
build-wasm (ubuntu-22.04)
cannot find function `bind` in module `sys::udp`
build-wasm (ubuntu-22.04)
cannot find function `only_v6` in module `sys::udp`
build-wasm (ubuntu-22.04)
cannot find function `set_reuseaddr` in this scope
build-wasm (ubuntu-22.04)
Process completed with exit code 101.
build-wasm (macos-14)
The job was canceled because "ubuntu-22_04" failed.
build-wasm (macos-14)
file not found for module `tcp`
build-wasm (macos-14)
file not found for module `udp`
build-wasm (macos-14)
the name `tcp` is defined multiple times
build-wasm (macos-14)
unresolved imports `crate::sys::tcp::bind`, `crate::sys::tcp::listen`, `crate::sys::tcp::new_for_addr`
build-wasm (macos-14)
unresolved imports `crate::sys::tcp::connect`, `crate::sys::tcp::new_for_addr`
build-wasm (macos-14)
cannot find function `bind` in module `sys::udp`
build-wasm (macos-14)
cannot find function `only_v6` in module `sys::udp`
build-wasm (macos-14)
cannot find function `set_reuseaddr` in this scope
build-wasm (macos-14)
Process completed with exit code 101.
build-wasm (macos-13)
The job was canceled because "ubuntu-22_04" failed.
build-wasm (macos-13)
The operation was canceled.
build-wasm (ubuntu-22.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/