Skip to content

LibWeb: Follow explicit cell widths when calculating fixed table layouts #30926

LibWeb: Follow explicit cell widths when calculating fixed table layouts

LibWeb: Follow explicit cell widths when calculating fixed table layouts #30926

Triggered via pull request May 28, 2026 08:41
Status Failure
Total duration 54m 14s
Artifacts 4

ci.yml

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

Annotations

1 error and 17 warnings
Linux, arm64, Sanitizer, Clang / CI
Process completed with exit code 8.
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, 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, 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, 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/
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, 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
294 KB
sha256:4d42ec079cc969f33b94384a9eb68c2aad65321e94426e9b2bfeaa6b314cc126
libweb-test-artifacts-Linux-x86_64-Release-GNU-false
260 KB
sha256:74337e555e5482860ddc03a532f6e08ff4be345cdc438183827eb22a532d433d
libweb-test-artifacts-Linux-x86_64-Sanitizer-Clang-true
286 KB
sha256:3e14be0c2381a2ce5b05251471f3cfb94918414e0b13309262fc895fe90c8793
libweb-test-artifacts-macOS-arm64-Sanitizer-Clang-false
387 KB
sha256:74337408801cf1d40c148cd8f775e4cf59a93f1fc565249e8a971eaf279748ad