The hosted runner: GitHub Actions 287 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.

Check with linter

The hosted runner: GitHub Actions 136 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.

Run e2e tests on Stencil.js sample

The hosted runner: GitHub Actions 68 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.

Run e2e tests on Atomic React

The hosted runner: GitHub Actions 381 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.

Run e2e tests on Atomic Angular

The hosted runner: GitHub Actions 354 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.

Run e2e tests on Vue.js sample

The hosted runner: GitHub Actions 297 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.

Run e2e tests on Headless SSR App router sample in dev mode

The hosted runner: GitHub Actions 356 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.

Run e2e tests on Headless SSR App router sample in prod mode

The hosted runner: GitHub Actions 403 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.

Run e2e tests on Headless SSR Pages router sample in dev mode

The hosted runner: GitHub Actions 314 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.

Run e2e tests on Headless SSR Pages router sample in prod mode

The hosted runner: GitHub Actions 181 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.

Run e2e tests for IIFE

The hosted runner: GitHub Actions 445 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.

Run e2e tests for Atomic Hosted Page

The hosted runner: GitHub Actions 323 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.

Run Playwright tests for Atomic (10, 24)

The hosted runner: GitHub Actions 261 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.

Run Playwright tests for Atomic (1, 24)

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.

Run Playwright tests for Atomic (11, 24)

The hosted runner: GitHub Actions 103 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.

Run Playwright tests for Atomic (13, 24)

The hosted runner: GitHub Actions 311 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.

Run Playwright tests for Atomic (12, 24)

The hosted runner: GitHub Actions 196 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.

Run Playwright tests for Atomic (14, 24)

The hosted runner: GitHub Actions 283 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.

Run Playwright tests for Atomic (17, 24)

The hosted runner: GitHub Actions 242 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.

Run Playwright tests for Atomic (15, 24)

The hosted runner: GitHub Actions 483 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.

Run Playwright tests for Atomic (19, 24)

The hosted runner: GitHub Actions 412 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.

Run Playwright tests for Atomic (2, 24)

The hosted runner: GitHub Actions 499 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.

Run Playwright tests for Atomic (20, 24)

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.

Run Playwright tests for Atomic (22, 24)

The hosted runner: GitHub Actions 113 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.

Run Playwright tests for Atomic (23, 24)

The hosted runner: GitHub Actions 451 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.

Run Playwright tests for Atomic (21, 24)

The hosted runner: GitHub Actions 111 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.

Run Playwright tests for Atomic (24, 24)

The hosted runner: GitHub Actions 147 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.

Run Playwright tests for Atomic (5, 24)

The hosted runner: GitHub Actions 12 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.

Run Playwright tests for Atomic (4, 24)

The hosted runner: GitHub Actions 168 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.

Run Playwright tests for Atomic (8, 24)

The hosted runner: GitHub Actions 65 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.

Run Playwright tests for Atomic (7, 24)

The hosted runner: GitHub Actions 262 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.

Run Playwright tests for Atomic (6, 24)

The hosted runner: GitHub Actions 115 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.

Run Playwright tests for Atomic (9, 24)

The hosted runner: GitHub Actions 325 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.

Should test Quantic?

The hosted runner: GitHub Actions 439 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.

Run e2e tests on Atomic (1)

The hosted runner: GitHub Actions 153 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.

Run e2e tests on Atomic (10)

The hosted runner: GitHub Actions 327 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.

Run e2e tests on Atomic (12)

The hosted runner: GitHub Actions 265 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.

Run e2e tests on Atomic (13)

The hosted runner: GitHub Actions 487 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.

Run e2e tests on Atomic (11)

The hosted runner: GitHub Actions 144 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.

Run e2e tests on Atomic (15)

The hosted runner: GitHub Actions 361 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.

Run e2e tests on Atomic (18)

The hosted runner: GitHub Actions 469 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.

Run e2e tests on Atomic (16)

The hosted runner: GitHub Actions 122 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.

Run e2e tests on Atomic (17)

The hosted runner: GitHub Actions 308 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.

Run e2e tests on Atomic (19)

The hosted runner: GitHub Actions 250 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.

Run e2e tests on Atomic (21)

The hosted runner: GitHub Actions 494 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.

Run e2e tests on Atomic (20)

The hosted runner: GitHub Actions 151 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.

Run e2e tests on Atomic (2)

The hosted runner: GitHub Actions 303 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.

Run e2e tests on Atomic (23)

The hosted runner: GitHub Actions 455 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.

Run e2e tests on Atomic (22)

The hosted runner: GitHub Actions 191 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.

Run e2e tests on Atomic (26)

The hosted runner: GitHub Actions 80 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.

Run e2e tests on Atomic (24)

The hosted runner: GitHub Actions 146 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.

Run e2e tests on Atomic (29)

The hosted runner: GitHub Actions 456 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.

Run e2e tests on Atomic (27)

The hosted runner: GitHub Actions 44 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.

Run e2e tests on Atomic (28)

The hosted runner: GitHub Actions 90 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.

Run e2e tests on Atomic (30)

The hosted runner: GitHub Actions 128 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.

Run e2e tests on Atomic (3)

The hosted runner: GitHub Actions 120 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.

Run e2e tests on Atomic (32)

The hosted runner: GitHub Actions 267 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.

Run e2e tests on Atomic (31)

The hosted runner: GitHub Actions 165 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.

Run e2e tests on Atomic (34)

The hosted runner: GitHub Actions 119 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.

Run e2e tests on Atomic (33)

The hosted runner: GitHub Actions 419 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.

Run e2e tests on Atomic (35)

The hosted runner: GitHub Actions 179 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.

Run e2e tests on Atomic (36)

The hosted runner: GitHub Actions 132 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.

Run e2e tests on Atomic (39)

The hosted runner: GitHub Actions 94 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.

Run e2e tests on Atomic (38)

The hosted runner: GitHub Actions 353 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.

Run e2e tests on Atomic (40)

The hosted runner: GitHub Actions 454 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.

Run e2e tests on Atomic (4)

The hosted runner: GitHub Actions 330 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.

Run e2e tests on Atomic (43)

The hosted runner: GitHub Actions 482 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.

Run e2e tests on Atomic (41)

The hosted runner: GitHub Actions 202 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.

Run e2e tests on Atomic (45)

The hosted runner: GitHub Actions 309 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.

Run e2e tests on Atomic (44)

The hosted runner: GitHub Actions 471 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.

Run e2e tests on Atomic (42)

The hosted runner: GitHub Actions 379 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.

Run e2e tests on Atomic (49)

The hosted runner: GitHub Actions 43 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.

Run e2e tests on Atomic (47)

The hosted runner: GitHub Actions 352 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.

Run e2e tests on Atomic (48)

The hosted runner: GitHub Actions 260 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.

Run e2e tests on Atomic (5)

The hosted runner: GitHub Actions 175 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.

Run e2e tests on Atomic (51)

The hosted runner: GitHub Actions 295 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.

Run e2e tests on Atomic (52)

The hosted runner: GitHub Actions 106 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.

Run e2e tests on Atomic (54)

The hosted runner: GitHub Actions 402 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.

Run e2e tests on Atomic (50)

The hosted runner: GitHub Actions 209 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.

Run e2e tests on Atomic (53)

The hosted runner: GitHub Actions 173 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.

Run e2e tests on Atomic (56)

The hosted runner: GitHub Actions 450 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.

Run e2e tests on Atomic (58)

The hosted runner: GitHub Actions 474 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.

Run e2e tests on Atomic (6)

The hosted runner: GitHub Actions 36 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.

Run e2e tests on Atomic (55)

The hosted runner: GitHub Actions 480 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.

Run e2e tests on Atomic (7)

The hosted runner: GitHub Actions 362 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.

Run e2e tests on Atomic (60)

The hosted runner: GitHub Actions 69 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.

Run e2e tests on Atomic (8)

The hosted runner: GitHub Actions 164 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.

Confirm build is valid (PR)

Process completed with exit code 1.

Confirm build is valid

Process completed with exit code 1.

Run e2e tests on Atomic (57)

The following actions use a deprecated Node.js version and will be forced to run on node20: cypress-io/github-action@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Run e2e tests on Atomic React NextJS