Run test262 in all engines and publish #788
Triggered via schedule
December 28, 2024 00:36
CanadaHonk
Status
Failure
Total duration
3h 14m 55s
Artifacts
44
Annotations
91 errors and 1 warning
|
test262 (jsc, 0)
Process completed with exit code 1.
|
|
test262 (jsc, 0)
Process completed with exit code 1.
|
|
test262 (jsc, 1)
Process completed with exit code 1.
|
|
test262 (jsc, 1)
Process completed with exit code 1.
|
|
test262 (v8_exp, 0)
Process completed with exit code 1.
|
|
test262 (v8_exp, 0)
Process completed with exit code 1.
|
|
test262 (jsc_exp, 0)
Process completed with exit code 1.
|
|
test262 (jsc_exp, 0)
Process completed with exit code 1.
|
|
test262 (v8, 1)
Process completed with exit code 1.
|
|
test262 (v8, 1)
Process completed with exit code 1.
|
|
test262 (v8_exp, 1)
Process completed with exit code 1.
|
|
test262 (v8_exp, 1)
Process completed with exit code 1.
|
|
test262 (v8, 0)
Process completed with exit code 1.
|
|
test262 (v8, 0)
Process completed with exit code 1.
|
|
test262 (sm_exp, 0)
Process completed with exit code 1.
|
|
test262 (sm_exp, 0)
Process completed with exit code 1.
|
|
test262 (sm_exp, 1)
Process completed with exit code 1.
|
|
test262 (sm_exp, 1)
Process completed with exit code 1.
|
|
test262 (jsc_exp, 1)
Process completed with exit code 1.
|
|
test262 (jsc_exp, 1)
Process completed with exit code 1.
|
|
test262 (sm, 0)
Process completed with exit code 1.
|
|
test262 (sm, 0)
Process completed with exit code 1.
|
|
test262 (hermes, 1)
Process completed with exit code 1.
|
|
test262 (hermes, 1)
Process completed with exit code 1.
|
|
test262 (sm, 1)
Process completed with exit code 1.
|
|
test262 (sm, 1)
Process completed with exit code 1.
|
|
test262 (chakra, 0)
Process completed with exit code 1.
|
|
test262 (chakra, 0)
Process completed with exit code 1.
|
|
test262 (hermes, 0)
Process completed with exit code 1.
|
|
test262 (hermes, 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 (kiesel, 0)
Process completed with exit code 1.
|
|
test262 (kiesel, 0)
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 (kiesel, 1)
Process completed with exit code 1.
|
|
test262 (kiesel, 1)
Process completed with exit code 1.
|
|
test262 (qjs_ng, 0)
Process completed with exit code 1.
|
|
test262 (qjs_ng, 0)
Process completed with exit code 1.
|
|
test262 (libjs, 1)
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 (qjs_ng, 1)
Process completed with exit code 1.
|
|
test262 (qjs_ng, 1)
Process completed with exit code 1.
|
|
test262 (engine262, 0)
Process completed with exit code 1.
|
|
test262 (engine262, 0)
Process completed with exit code 1.
|
|
test262 (qjs, 0)
Process completed with exit code 1.
|
|
test262 (qjs, 0)
Process completed with exit code 1.
|
|
test262 (qjs, 1)
Process completed with exit code 1.
|
|
test262 (qjs, 1)
Process completed with exit code 1.
|
|
test262 (xs, 0)
Process completed with exit code 1.
|
|
test262 (xs, 0)
Process completed with exit code 1.
|
|
test262 (xs, 1)
Process completed with exit code 1.
|
|
test262 (xs, 1)
Process completed with exit code 1.
|
|
test262 (engine262, 1)
Process completed with exit code 1.
|
|
test262 (engine262, 1)
Process completed with exit code 1.
|
|
test262 (graaljs, 0)
Process completed with exit code 1.
|
|
test262 (graaljs, 0)
Process completed with exit code 1.
|
|
test262 (graaljs, 1)
Process completed with exit code 1.
|
|
test262 (graaljs, 1)
Process completed with exit code 1.
|
|
test262 (boa, 1)
Process completed with exit code 1.
|
|
test262 (boa, 1)
Process completed with exit code 1.
|
|
test262 (boa, 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 (boa, 0)
The operation was canceled.
|
|
test262 (rhino, 1)
Process completed with exit code 1.
|
|
test262 (rhino, 1)
Process completed with exit code 1.
|
|
test262 (rhino, 0)
Process completed with exit code 1.
|
|
test262 (rhino, 0)
Process completed with exit code 1.
|
|
test262 (nova, 0)
Process completed with exit code 1.
|
|
test262 (nova, 0)
Process completed with exit code 1.
|
|
test262 (njs, 1)
Process completed with exit code 1.
|
|
test262 (njs, 1)
Process completed with exit code 1.
|
|
test262 (njs, 0)
Process completed with exit code 1.
|
|
test262 (njs, 0)
Process completed with exit code 1.
|
|
test262 (bali, 0)
Process completed with exit code 1.
|
|
test262 (bali, 0)
Process completed with exit code 1.
|
|
test262 (nova, 1)
Process completed with exit code 1.
|
|
test262 (nova, 1)
Process completed with exit code 1.
|
|
test262 (bali, 1)
Process completed with exit code 1.
|
|
test262 (bali, 1)
Process completed with exit code 1.
|
|
test262 (swc, 0)
Process completed with exit code 1.
|
|
test262 (swc, 0)
Process completed with exit code 1.
|
|
test262 (sucrase, 1)
Process completed with exit code 1.
|
|
test262 (sucrase, 1)
Process completed with exit code 1.
|
|
test262 (sucrase, 0)
Process completed with exit code 1.
|
|
test262 (sucrase, 0)
Process completed with exit code 1.
|
|
test262 (babel, 0)
Process completed with exit code 1.
|
|
test262 (babel, 0)
Process completed with exit code 1.
|
|
test262 (babel, 1)
Process completed with exit code 1.
|
|
test262 (babel, 1)
Process completed with exit code 1.
|
|
test262 (swc, 1)
Process completed with exit code 1.
|
|
test262 (swc, 1)
Process completed with exit code 1.
|
|
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", "boa1", "chakra0", "chakra1", "chunks", "engine2620", "engine2621", "graaljs0", "graaljs1", "hermes0", "hermes1", "jsc_exp0", "jsc_exp1", "jsc0", "jsc1", "kiesel0", "kiesel1", "njs0", "njs1", "nova0", "nova1", "qjs_ng0", "qjs_ng1", "qjs0", "qjs1", "rhino0", "rhino1", "sm_exp0", "sm_exp1", "sm0", "sm1", "sucrase0", "sucrase1", "swc0", "swc1", "v8_exp0", "v8_exp1", "v80", "v81", "xs0", "xs1".
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.8 MB |
|
|
babel1
|
44.4 MB |
|
|
bali0
|
39.5 MB |
|
|
bali1
|
46.3 MB |
|
|
boa1
|
43.4 MB |
|
|
chakra0
|
43 Bytes |
|
|
chakra1
|
44 Bytes |
|
|
chunks
|
3.56 MB |
|
|
engine2620
|
36.4 MB |
|
|
engine2621
|
43.8 MB |
|
|
graaljs0
|
36.1 MB |
|
|
graaljs1
|
43.4 MB |
|
|
hermes0
|
83 Bytes |
|
|
hermes1
|
84 Bytes |
|
|
jsc0
|
43 Bytes |
|
|
jsc1
|
44 Bytes |
|
|
jsc_exp0
|
43 Bytes |
|
|
jsc_exp1
|
44 Bytes |
|
|
kiesel0
|
146 Bytes |
|
|
kiesel1
|
147 Bytes |
|
|
njs0
|
39.4 MB |
|
|
njs1
|
46.8 MB |
|
|
nova0
|
39.9 MB |
|
|
nova1
|
47.5 MB |
|
|
qjs0
|
36.3 MB |
|
|
qjs1
|
43.6 MB |
|
|
qjs_ng0
|
36.3 MB |
|
|
qjs_ng1
|
43.5 MB |
|
|
rhino0
|
37.1 MB |
|
|
rhino1
|
44.5 MB |
|
|
sm0
|
43 Bytes |
|
|
sm1
|
44 Bytes |
|
|
sm_exp0
|
43 Bytes |
|
|
sm_exp1
|
44 Bytes |
|
|
sucrase0
|
38.9 MB |
|
|
sucrase1
|
45.7 MB |
|
|
swc0
|
47.6 MB |
|
|
swc1
|
45.7 MB |
|
|
v80
|
36.1 MB |
|
|
v81
|
43.3 MB |
|
|
v8_exp0
|
36 MB |
|
|
v8_exp1
|
43 MB |
|
|
xs0
|
43 Bytes |
|
|
xs1
|
44 Bytes |
|