Skip to content

Run Next.js repo tests #410

Run Next.js repo tests

Run Next.js repo tests #410

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Manually triggered August 29, 2024 19:40
Status Failure
Total duration 1h 21m 7s
Artifacts

test-e2e.yml

on: workflow_dispatch
Matrix: e2e
Matrix: publish-test-results
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
Test next@latest group 11/12
Process completed with exit code 1.
Test next@latest group 2/12
The hosted runner: GitHub Actions 345 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.
Test next@canary group 7/12
Process completed with exit code 1.
Test next@latest group 5/12
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Test next@latest group 5/12
Process completed with exit code 143.
Test next@latest group 9/12
The hosted runner: GitHub Actions 407 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.
Test next@canary group 12/12
The template is not valid. .github/workflows/test-e2e.yml (Line: 146, Col: 16): hashFiles('next-runtime/package-lock.json') failed. Fail to hash files under directory '/home/runner/work/next-runtime/next-runtime'
Test next@canary group 12/12
An error occurred trying to start process '/home/runner/runners/2.319.1/externals/node20/bin/node' with working directory '/home/runner/work/next-runtime/next-runtime'. Resource temporarily unavailable
Test next@canary group 12/12
An error occurred trying to start process '/home/runner/runners/2.319.1/externals/node20/bin/node' with working directory '/home/runner/work/next-runtime/next-runtime'. Resource temporarily unavailable
Test next@canary group 5/12
The hosted runner: GitHub Actions 378 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.
Test next@canary group 5/12
Process completed with exit code 1.
Test next@latest group 11/12
No files were found with the provided path: next.js/test/test-junit-report/*.xml. No artifacts will be uploaded.
Test next@canary group 7/12
The process '/usr/bin/git' failed with exit code 128