Skip to content

Bump serve-static and express in /website/client #19925

Bump serve-static and express in /website/client

Bump serve-static and express in /website/client #19925

Triggered via pull request September 16, 2024 21:28
Status Failure
Total duration 50m 3s
Artifacts

test.yml

on: pull_request
Matrix: api-unit
Matrix: api-v3-integration
Matrix: api-v4-integration
Matrix: apidoc
Matrix: client-unit
Matrix: common
Matrix: content
Matrix: lint
Matrix: production-build
Matrix: sanity
Fit to window
Zoom out
Zoom in

Annotations

7 errors
apidoc (21.x)
The hosted runner: GitHub Actions 40 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
api-v3-integration (21.x, 4.2)
The hosted runner: GitHub Actions 59 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
api-unit (21.x, 4.2)
The hosted runner: GitHub Actions 10 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
lint (21.x)
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
client-unit (21.x)
The hosted runner: GitHub Actions 16 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
production-build (21.x)
The hosted runner: GitHub Actions 22 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
api-v4-integration (21.x, 4.2)
The hosted runner: GitHub Actions 25 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.