Run test262 in all engines and publish #803
CanadaHonkAnnotations
41 errors and 1 warning
|
test262 (bali, 0)
Process completed with exit code 1.
|
|
test262 (bali, 0)
Process completed with exit code 1.
|
|
test262 (boa, 0)
Process completed with exit code 1.
|
|
test262 (boa, 0)
Process completed with exit code 1.
|
|
test262 (chakra, 1)
Process completed with exit code 1.
|
|
test262 (chakra, 1)
Process completed with exit code 1.
|
|
test262 (bali, 1)
Process completed with exit code 1.
|
|
test262 (boa, 1)
Process completed with exit code 1.
|
|
test262 (chakra, 0)
Process completed with exit code 1.
|
|
test262 (babel, 1)
Process completed with exit code 1.
|
|
test262 (hermes, 1)
Process completed with exit code 1.
|
|
test262 (engine262, 1)
Process completed with exit code 1.
|
|
test262 (hermes, 0)
Process completed with exit code 1.
|
|
test262 (graaljs, 0)
Process completed with exit code 1.
|
|
test262 (jsc, 0)
Process completed with exit code 1.
|
|
test262 (jsc_exp, 0)
Process completed with exit code 1.
|
|
test262 (kiesel, 0)
Process completed with exit code 1.
|
|
test262 (libjs, 1)
Process completed with exit code 1.
|
|
test262 (libjs, 0)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
test262 (libjs, 0)
The operation was canceled.
|
|
test262 (njs, 0)
Process completed with exit code 1.
|
|
test262 (nova, 0)
Process completed with exit code 1.
|
|
test262 (qjs_ng, 1)
Process completed with exit code 1.
|
|
test262 (qjs, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (qjs, 1)
Process completed with exit code 1.
|
|
test262 (sm, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (sm, 1)
The self-hosted runner: runner-3@izumi 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.
|
|
test262 (rhino, 0)
The self-hosted runner: runner-2@izumi 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.
|
|
test262 (rhino, 1)
The self-hosted runner: runner-0@izumi 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.
|
|
test262 (sucrase, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (sm_exp, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (sm_exp, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (swc, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (sucrase, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (v8, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (v8, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (swc, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (v8_exp, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (v8_exp, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (xs, 1)
The self-hosted runner: runner-1@izumi 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.
|
|
test262 (xs, 0)
The self-hosted runner: runner-1@izumi 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.
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "babel0", "babel1", "bali0", "bali1", "boa0", "boa1", "chakra0", "chakra1", "chunks", "engine2620", "engine2621", "github-pages", "graaljs0", "graaljs1", "hermes0", "hermes1", "jsc_exp0", "jsc_exp1", "jsc0", "jsc1", "kiesel0", "kiesel1", "libjs1", "njs0", "njs1", "nova0", "nova1", "qjs_ng0", "qjs_ng1", "qjs1".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
babel0
|
36.9 MB |
|
|
babel1
|
44.4 MB |
|
|
bali0
|
39.6 MB |
|
|
bali1
|
46.3 MB |
|
|
boa0
|
41 Bytes |
|
|
boa1
|
43.5 MB |
|
|
chakra0
|
38 MB |
|
|
chakra1
|
45.3 MB |
|
|
chunks
|
3.57 MB |
|
|
engine2620
|
36.6 MB |
|
|
engine2621
|
43.8 MB |
|
|
github-pages
Expired
|
12.2 MB |
|
|
graaljs0
|
36.2 MB |
|
|
graaljs1
|
43.5 MB |
|
|
hermes0
|
83 Bytes |
|
|
hermes1
|
84 Bytes |
|
|
jsc0
|
36.2 MB |
|
|
jsc1
|
43.3 MB |
|
|
jsc_exp0
|
36.2 MB |
|
|
jsc_exp1
|
43.3 MB |
|
|
kiesel0
|
36.9 MB |
|
|
kiesel1
|
44 MB |
|
|
libjs1
|
42.7 MB |
|
|
njs0
|
39.6 MB |
|
|
njs1
|
46.8 MB |
|
|
nova0
|
39.5 MB |
|
|
nova1
|
47.3 MB |
|
|
qjs1
|
43.6 MB |
|
|
qjs_ng0
|
36.4 MB |
|
|
qjs_ng1
|
43.5 MB |
|