E2E | os: Linux | browser: chrome | network: preprod | #983 | tags: | smoke only: false #983
e2e-tests-linux-split.yml
on: workflow_dispatch
Annotations
122 errors
E2E tests (11)
Process completed with exit code 1.
|
E2E tests (11)
Process completed with exit code 1.
|
E2E tests (14)
Process completed with exit code 1.
|
E2E tests (12)
Process completed with exit code 1.
|
E2E tests (10)
Process completed with exit code 1.
|
E2E tests (10)
Process completed with exit code 1.
|
E2E tests (15)
Process completed with exit code 1.
|
E2E tests (15)
Process completed with exit code 1.
|
E2E tests (16)
Process completed with exit code 1.
|
E2E tests (16)
Process completed with exit code 1.
|
E2E tests (19)
Process completed with exit code 1.
|
E2E tests (19)
Process completed with exit code 1.
|
E2E tests (1)
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 (1)
The operation was canceled.
|
E2E tests (1)
The self-hosted runner: lace-setup-runner-5lgg9-gvgrs 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 (17)
Process completed with exit code 1.
|
E2E tests (17)
Process completed with exit code 1.
|
E2E tests (18)
Process completed with exit code 1.
|
E2E tests (18)
Process completed with exit code 1.
|
E2E tests (21)
Process completed with exit code 1.
|
E2E tests (21)
Process completed with exit code 1.
|
E2E tests (20)
Process completed with exit code 1.
|
E2E tests (20)
Process completed with exit code 1.
|
E2E tests (13)
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 (13)
The self-hosted runner: lace-setup-runner-5lgg9-9wmn5 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 (22)
Process completed with exit code 1.
|
E2E tests (22)
Process completed with exit code 1.
|
E2E tests (23)
Process completed with exit code 1.
|
E2E tests (23)
Process completed with exit code 1.
|
E2E tests (24)
Process completed with exit code 1.
|
E2E tests (24)
Process completed with exit code 1.
|
E2E tests (26)
Process completed with exit code 1.
|
E2E tests (26)
Process completed with exit code 1.
|
E2E tests (25)
Process completed with exit code 1.
|
E2E tests (25)
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 (2)
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 (2)
The self-hosted runner: lace-setup-runner-5lgg9-wt9jz 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 (28)
Process completed with exit code 1.
|
E2E tests (28)
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 (3)
Process completed with exit code 1.
|
E2E tests (3)
Process completed with exit code 1.
|
E2E tests (30)
Process completed with exit code 1.
|
E2E tests (30)
Process completed with exit code 1.
|
E2E tests (33)
Process completed with exit code 1.
|
E2E tests (31)
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 (32)
Process completed with exit code 1.
|
E2E tests (34)
Process completed with exit code 1.
|
E2E tests (34)
Process completed with exit code 1.
|
E2E tests (35)
Process completed with exit code 1.
|
E2E tests (35)
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 (37)
Process completed with exit code 1.
|
E2E tests (39)
Process completed with exit code 1.
|
E2E tests (39)
Process completed with exit code 1.
|
E2E tests (38)
Process completed with exit code 1.
|
E2E tests (38)
Process completed with exit code 1.
|
E2E tests (4)
Process completed with exit code 1.
|
E2E tests (4)
Process completed with exit code 1.
|
E2E tests (40)
Process completed with exit code 1.
|
E2E tests (40)
Process completed with exit code 1.
|
E2E tests (45)
Process completed with exit code 1.
|
E2E tests (45)
Process completed with exit code 1.
|
E2E tests (47)
Process completed with exit code 1.
|
E2E tests (47)
Process completed with exit code 1.
|
E2E tests (42)
Process completed with exit code 1.
|
E2E tests (42)
Process completed with exit code 1.
|
E2E tests (46)
Process completed with exit code 1.
|
E2E tests (46)
Process completed with exit code 1.
|
E2E tests (43)
Process completed with exit code 1.
|
E2E tests (43)
Process completed with exit code 1.
|
E2E tests (5)
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 (50)
Process completed with exit code 1.
|
E2E tests (41)
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 (41)
The self-hosted runner: lace-setup-runner-5lgg9-pfxb7 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 (44)
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 (44)
The self-hosted runner: lace-setup-runner-5lgg9-6fj8n 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 (52)
Process completed with exit code 1.
|
E2E tests (52)
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 (49)
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 (49)
The self-hosted runner: lace-setup-runner-5lgg9-kvx5s 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 (54)
Process completed with exit code 1.
|
E2E tests (56)
Process completed with exit code 1.
|
E2E tests (56)
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 (58)
Process completed with exit code 1.
|
E2E tests (58)
Process completed with exit code 1.
|
E2E tests (55)
Process completed with exit code 1.
|
E2E tests (55)
Process completed with exit code 1.
|
E2E tests (48)
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 (48)
The self-hosted runner: lace-setup-runner-5lgg9-vkc4q 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 (51)
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 (51)
The self-hosted runner: lace-setup-runner-5lgg9-kc2pk 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 (6)
Process completed with exit code 1.
|
E2E tests (6)
Process completed with exit code 1.
|
E2E tests (59)
Process completed with exit code 1.
|
E2E tests (59)
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 (62)
Process completed with exit code 1.
|
E2E tests (62)
Process completed with exit code 1.
|
E2E tests (61)
Process completed with exit code 1.
|
E2E tests (61)
Process completed with exit code 1.
|
E2E tests (7)
Process completed with exit code 1.
|
E2E tests (7)
Process completed with exit code 1.
|
E2E tests (8)
Process completed with exit code 1.
|
E2E tests (8)
Process completed with exit code 1.
|
E2E tests (9)
Process completed with exit code 1.
|
E2E tests (9)
Process completed with exit code 1.
|
Process e2e test reports
The run was canceled by @bernokl.
|
Process e2e test reports
The operation was canceled.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
runner-artifacts-10
Expired
|
834 Bytes |
|
runner-artifacts-11
Expired
|
484 Bytes |
|
runner-artifacts-12
Expired
|
134 Bytes |
|
runner-artifacts-15
Expired
|
1.06 KB |
|
runner-artifacts-16
Expired
|
484 Bytes |
|
runner-artifacts-17
Expired
|
1.06 KB |
|
runner-artifacts-18
Expired
|
1.36 KB |
|
runner-artifacts-19
Expired
|
1.5 KB |
|
runner-artifacts-20
Expired
|
1.84 KB |
|
runner-artifacts-21
Expired
|
1.16 KB |
|
runner-artifacts-22
Expired
|
1.2 KB |
|
runner-artifacts-23
Expired
|
834 Bytes |
|
runner-artifacts-24
Expired
|
484 Bytes |
|
runner-artifacts-25
Expired
|
1.06 KB |
|
runner-artifacts-26
Expired
|
1.05 KB |
|
runner-artifacts-27
Expired
|
2.08 KB |
|
runner-artifacts-28
Expired
|
834 Bytes |
|
runner-artifacts-29
Expired
|
834 Bytes |
|
runner-artifacts-3
Expired
|
834 Bytes |
|
runner-artifacts-30
Expired
|
1.06 KB |
|
runner-artifacts-31
Expired
|
1.06 KB |
|
runner-artifacts-32
Expired
|
1.4 KB |
|
runner-artifacts-33
Expired
|
134 Bytes |
|
runner-artifacts-34
Expired
|
484 Bytes |
|
runner-artifacts-35
Expired
|
484 Bytes |
|
runner-artifacts-36
Expired
|
134 Bytes |
|
runner-artifacts-37
Expired
|
484 Bytes |
|
runner-artifacts-38
Expired
|
1.36 KB |
|
runner-artifacts-39
Expired
|
1.21 KB |
|
runner-artifacts-4
Expired
|
834 Bytes |
|
runner-artifacts-40
Expired
|
834 Bytes |
|
runner-artifacts-42
Expired
|
1.21 KB |
|
runner-artifacts-43
Expired
|
1.7 KB |
|
runner-artifacts-45
Expired
|
834 Bytes |
|
runner-artifacts-46
Expired
|
834 Bytes |
|
runner-artifacts-47
Expired
|
484 Bytes |
|
runner-artifacts-5
Expired
|
1.06 KB |
|
runner-artifacts-50
Expired
|
1.06 KB |
|
runner-artifacts-52
Expired
|
2.23 KB |
|
runner-artifacts-53
Expired
|
484 Bytes |
|
runner-artifacts-54
Expired
|
134 Bytes |
|
runner-artifacts-55
Expired
|
1.21 KB |
|
runner-artifacts-56
Expired
|
1.06 KB |
|
runner-artifacts-57
Expired
|
134 Bytes |
|
runner-artifacts-58
Expired
|
1.4 KB |
|
runner-artifacts-59
Expired
|
1.06 KB |
|
runner-artifacts-6
Expired
|
1.06 KB |
|
runner-artifacts-60
Expired
|
1.51 KB |
|
runner-artifacts-61
Expired
|
2.34 KB |
|
runner-artifacts-62
Expired
|
1.21 KB |
|
runner-artifacts-7
Expired
|
1.06 KB |
|
runner-artifacts-8
Expired
|
1.21 KB |
|
runner-artifacts-9
Expired
|
134 Bytes |
|