Skip to content
Quality

docs: add changelog #5188

Sign in to view logs

docs: add changelog

docs: add changelog #5188

Triggered via push September 16, 2024 21:08
@segunadebayosegunadebayo
pushed e8dfb0f
main
Status Failure
Total duration 50m 5s
Artifacts –

quality.yml

on: push
Unit Tests
0s
Unit Tests
ESLint
0s
ESLint
TypeScript
2m 5s
TypeScript
Matrix: End-to-end Tests
Fit to window
Zoom out
Zoom in

Annotations

13 errors, 2 warnings, and 1 notice
Unit Tests
The hosted runner: GitHub Actions 7 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.
End-to-end Tests (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.
End-to-end Tests (7)
The hosted runner: GitHub Actions 9 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.
End-to-end Tests (4)
The hosted runner: GitHub Actions 13 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.
ESLint
The hosted runner: GitHub Actions 19 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.
End-to-end Tests (9)
The hosted runner: GitHub Actions 14 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.
End-to-end Tests (1)
The hosted runner: GitHub Actions 24 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.
End-to-end Tests (10)
The hosted runner: GitHub Actions 28 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.
End-to-end Tests (6)
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.
End-to-end Tests (11)
The hosted runner: GitHub Actions 33 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.
End-to-end Tests (12)
The hosted runner: GitHub Actions 34 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.
End-to-end Tests (5)
The hosted runner: GitHub Actions 31 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.
End-to-end Tests (8)
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.
TypeScript
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
End-to-end Tests (3)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
🎭 Playwright Run Summary
31 passed (50.7s)