Skip to content

Add tcp_socket::bind() for local endpoint binding before connect #47

Add tcp_socket::bind() for local endpoint binding before connect

Add tcp_socket::bind() for local endpoint binding before connect #47

Triggered via push April 6, 2026 20:52
Status Success
Total duration 5m 34s
Artifacts 3
Coverage (Linux)
2m 26s
Coverage (Linux)
Coverage (macOS)
3m 16s
Coverage (macOS)
Coverage (Windows)
5m 3s
Coverage (Windows)
Deploy Coverage
24s
Deploy Coverage
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Coverage (Linux)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Coverage (macOS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, alandefreitas/cpp-actions/boost-clone@v1.9.0, alandefreitas/cpp-actions/cmake-workflow@v1.9.0, alandefreitas/cpp-actions/setup-cpp@v1.9.0, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Coverage (macOS)
WolfSSL not found - TLS tests will be skipped
Coverage (macOS)
[LogCollection][Warn]File not found:'-- Loading CMake variables from /Users/runner/work/corosio/corosio/vcpkg/buildtrees/wolfssl/cmake-get-vars_C_CXX-arm64-osx.cmake.log'.
Coverage (Windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, alandefreitas/cpp-actions/boost-clone@v1.9.0, alandefreitas/cpp-actions/cmake-workflow@v1.9.0, alandefreitas/cpp-actions/setup-cpp@v1.9.0, lukka/run-vcpkg@v11. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Coverage (Windows)
WolfSSL not found - TLS tests will be skipped
Coverage (Windows)
[LogCollection][Warn]File not found:'-- Loading CMake variables from D:/a/corosio/corosio/vcpkg/buildtrees/wolfssl/cmake-get-vars_C_CXX-x64-mingw-static.cmake.log'.
Deploy Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
coverage-linux
3.09 MB
sha256:8632df87236b59face21e37ef4576680c23c5ad84b738a70d01463c786e4bf74
coverage-macos
3.69 MB
sha256:7cc3a194fe9f214a5d210d5ba4525797b31a8d5d83f58e186517f5a73cf451d5
coverage-windows
2.91 MB
sha256:eabc6cb8294b2fae49d45da8b27e21bd944f7b8ff3e30719b5318687970cd8a7