Skip to content

E2E | os: Linux | browser: chrome | network: preprod | #985 | tags: | smoke only: false #985

E2E | os: Linux | browser: chrome | network: preprod | #985 | tags: | smoke only: false

E2E | os: Linux | browser: chrome | network: preprod | #985 | tags: | smoke only: false #985

Manually triggered January 21, 2025 22:00
Status Cancelled
Total duration 2h 14m 36s
Artifacts 53

e2e-tests-linux-split.yml

on: workflow_dispatch
Build Lace
12s
Build Lace
Matrix: E2E tests
Process e2e test reports
0s
Process e2e test reports
Fit to window
Zoom out
Zoom in

Annotations

78 errors and 4 warnings
E2E tests (11)
Process completed with exit code 1.
E2E tests (12)
Process completed with exit code 1.
E2E tests (14)
Process completed with exit code 1.
E2E tests (10)
Process completed with exit code 1.
E2E tests (13)
Process completed with exit code 1.
E2E tests (1)
Process completed with exit code 1.
E2E tests (16)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (16)
The self-hosted runner: lace-setup-runner-nq5nj-4b85m lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (15)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (15)
The self-hosted runner: lace-setup-runner-nq5nj-9swbs lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (18)
Process completed with exit code 1.
E2E tests (21)
Process completed with exit code 1.
E2E tests (19)
Process completed with exit code 1.
E2E tests (17)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (17)
The self-hosted runner: lace-setup-runner-nq5nj-4sq4w lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (2)
Process completed with exit code 1.
E2E tests (22)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (22)
The operation was canceled.
E2E tests (20)
Process completed with exit code 1.
E2E tests (24)
Process completed with exit code 1.
E2E tests (25)
Process completed with exit code 1.
E2E tests (28)
Process completed with exit code 1.
E2E tests (26)
Process completed with exit code 1.
E2E tests (23)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (23)
The self-hosted runner: lace-setup-runner-nq5nj-l8lvn lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (30)
Process completed with exit code 1.
E2E tests (29)
Process completed with exit code 1.
E2E tests (29)
Process completed with exit code 1.
E2E tests (27)
Process completed with exit code 1.
E2E tests (27)
Process completed with exit code 1.
E2E tests (3)
Process completed with exit code 1.
E2E tests (31)
Process completed with exit code 1.
E2E tests (32)
Process completed with exit code 1.
E2E tests (33)
Process completed with exit code 1.
E2E tests (34)
Process completed with exit code 1.
E2E tests (36)
Process completed with exit code 1.
E2E tests (37)
Process completed with exit code 1.
E2E tests (38)
Process completed with exit code 1.
E2E tests (35)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (35)
The self-hosted runner: lace-setup-runner-nq5nj-d4rqg lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (39)
Process completed with exit code 1.
E2E tests (41)
Process completed with exit code 1.
E2E tests (41)
Process completed with exit code 1.
E2E tests (40)
Process completed with exit code 1.
E2E tests (4)
Process completed with exit code 1.
E2E tests (42)
Process completed with exit code 1.
E2E tests (43)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (43)
The operation was canceled.
E2E tests (45)
Process completed with exit code 1.
E2E tests (47)
Process completed with exit code 1.
E2E tests (46)
Process completed with exit code 1.
E2E tests (49)
Process completed with exit code 1.
E2E tests (48)
Process completed with exit code 1.
E2E tests (44)
Process completed with exit code 1.
E2E tests (44)
Process completed with exit code 1.
E2E tests (5)
Process completed with exit code 1.
E2E tests (50)
Process completed with exit code 1.
E2E tests (54)
Process completed with exit code 1.
E2E tests (51)
Process completed with exit code 1.
E2E tests (56)
Process completed with exit code 1.
E2E tests (53)
Process completed with exit code 1.
E2E tests (53)
Process completed with exit code 1.
E2E tests (57)
Process completed with exit code 1.
E2E tests (57)
Process completed with exit code 1.
E2E tests (52)
Process completed with exit code 1.
E2E tests (58)
Process completed with exit code 1.
E2E tests (59)
Process completed with exit code 1.
E2E tests (55)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
E2E tests (55)
The self-hosted runner: lace-setup-runner-nq5nj-ql6pb lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
E2E tests (7)
Process completed with exit code 1.
E2E tests (6)
Process completed with exit code 1.
E2E tests (60)
Process completed with exit code 1.
E2E tests (60)
Process completed with exit code 1.
E2E tests (9)
Process completed with exit code 1.
E2E tests (9)
Process completed with exit code 1.
E2E tests (8)
Process completed with exit code 1.
E2E tests (61)
The run was canceled by @bernokl.
E2E tests (62)
The run was canceled by @bernokl.
E2E tests (57)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 21 MB
E2E tests (58)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 6 MB
E2E tests (55)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 17 MB
E2E tests (62)
Runner lace-setup-runner-nq5nj-c9mqv did not respond to a cancelation request with 00:05:00.

Artifacts

Produced during runtime
Name Size
runner-artifacts-1 Expired
126 KB
runner-artifacts-10 Expired
22.4 KB
runner-artifacts-11 Expired
4.7 KB
runner-artifacts-12 Expired
134 Bytes
runner-artifacts-13 Expired
17.9 KB
runner-artifacts-14 Expired
17.5 KB
runner-artifacts-18 Expired
130 KB
runner-artifacts-19 Expired
222 KB
runner-artifacts-2 Expired
525 KB
runner-artifacts-20 Expired
590 KB
runner-artifacts-21 Expired
178 KB
runner-artifacts-24 Expired
11.2 KB
runner-artifacts-25 Expired
60.4 KB
runner-artifacts-26 Expired
294 KB
runner-artifacts-27 Expired
703 KB
runner-artifacts-28 Expired
67 KB
runner-artifacts-29 Expired
1.05 MB
runner-artifacts-3 Expired
31.3 KB
runner-artifacts-30 Expired
39.6 KB
runner-artifacts-31 Expired
27.2 KB
runner-artifacts-32 Expired
50.4 KB
runner-artifacts-33 Expired
134 Bytes
runner-artifacts-34 Expired
17.3 KB
runner-artifacts-36 Expired
134 Bytes
runner-artifacts-37 Expired
7.42 KB
runner-artifacts-38 Expired
143 KB
runner-artifacts-39 Expired
870 KB
runner-artifacts-4 Expired
406 KB
runner-artifacts-40 Expired
33.4 KB
runner-artifacts-41 Expired
134 Bytes
runner-artifacts-42 Expired
72.6 KB
runner-artifacts-44 Expired
237 KB
runner-artifacts-45 Expired
25.5 KB
runner-artifacts-46 Expired
122 KB
runner-artifacts-47 Expired
7.64 KB
runner-artifacts-48 Expired
15.5 KB
runner-artifacts-49 Expired
18 KB
runner-artifacts-5 Expired
54.3 KB
runner-artifacts-50 Expired
37.9 KB
runner-artifacts-51 Expired
38.2 KB
runner-artifacts-52 Expired
131 KB
runner-artifacts-53 Expired
57.4 KB
runner-artifacts-54 Expired
134 Bytes
runner-artifacts-56 Expired
5.79 KB
runner-artifacts-57 Expired
134 Bytes
runner-artifacts-58 Expired
78 KB
runner-artifacts-59 Expired
61 KB
runner-artifacts-6 Expired
148 KB
runner-artifacts-60 Expired
856 KB
runner-artifacts-61 Expired
396 KB
runner-artifacts-7 Expired
10.7 KB
runner-artifacts-8 Expired
15.4 KB
runner-artifacts-9 Expired
134 Bytes