Skip to content

LibProxy+LibWebview: Add System Proxy Support #30932

LibProxy+LibWebview: Add System Proxy Support

LibProxy+LibWebview: Add System Proxy Support #30932

Triggered via pull request May 28, 2026 09:59
Status Failure
Total duration 1h 31m 7s
Artifacts 4

ci.yml

on: pull_request
Matrix: Lagom
Fit to window
Zoom out
Zoom in

Annotations

1 error and 17 warnings
macOS, arm64, Sanitizer, Clang / CI
Process completed with exit code 8.
Linux, x86_64, Fuzzers, Clang / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
Linux, x86_64, Release, GNU / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
Windows, x86_64, Sanitizer, ClangCL / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
Linux, x86_64, Sanitizer, Clang / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
Linux, x86_64, All_Debug, Clang / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
Linux, arm64, Sanitizer, Clang / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
macOS, arm64, Sanitizer, Clang / CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@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/
macOS, arm64, Sanitizer, Clang / CI
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
macOS, arm64, Sanitizer, Clang / CI
nasm 3.01 is already installed and up-to-date. To reinstall 3.01, run: brew reinstall nasm
macOS, arm64, Sanitizer, Clang / CI
llvm@21 21.1.8 is already installed and up-to-date. To reinstall 21.1.8, run: brew reinstall llvm@21
macOS, arm64, Sanitizer, Clang / CI
libtool 2.5.4 is already installed and up-to-date. To reinstall 2.5.4, run: brew reinstall libtool
macOS, arm64, Sanitizer, Clang / CI
coreutils 9.11 is already installed and up-to-date. To reinstall 9.11, run: brew reinstall coreutils
macOS, arm64, Sanitizer, Clang / CI
ccache 4.13.6 is already installed and up-to-date. To reinstall 4.13.6, run: brew reinstall ccache
macOS, arm64, Sanitizer, Clang / CI
bash 5.3.9 is already installed and up-to-date. To reinstall 5.3.9, run: brew reinstall bash
macOS, arm64, Sanitizer, Clang / CI
automake 1.18.1 is already installed and up-to-date. To reinstall 1.18.1, run: brew reinstall automake
macOS, arm64, Sanitizer, Clang / CI
autoconf-archive 2024.10.16 is already installed and up-to-date. To reinstall 2024.10.16, run: brew reinstall autoconf-archive
macOS, arm64, Sanitizer, Clang / CI
autoconf 2.73 is already installed and up-to-date. To reinstall 2.73, run: brew reinstall autoconf

Artifacts

Produced during runtime
Name Size Digest
libweb-test-artifacts-Linux-arm64-Sanitizer-Clang-false
300 KB
sha256:791d31254f00d98d89cd2143abef7d12265d1e168e775a408b9b900bc76e5612
libweb-test-artifacts-Linux-x86_64-Release-GNU-false
271 KB
sha256:d475375068cd82cfdffda20630dff0ed10a6b7e0b5789a78af65166a4148448e
libweb-test-artifacts-Linux-x86_64-Sanitizer-Clang-true
296 KB
sha256:00689713d9b563b17bbaebb3bf8d8e220b10e816360e77cb823cfe5fdd3da5d7
libweb-test-artifacts-macOS-arm64-Sanitizer-Clang-false
401 KB
sha256:df7799aa4ce0e81d52bf1ae3f529a0d2bde15cc0aecc6319103dcb5565798489