Skip to content

Run-Core

Run-Core #90

Triggered via schedule March 29, 2026 10:09
Status Failure
Total duration 13m 29s
Artifacts

run_core.yml

on: schedule
Matrix: call-suite-core / call-ci-bazel / bazel_tests
Matrix: call-suite-core / call-ci-makefile / x86_makefile_tests
call-suite-core  /  ...  /  Code Style
1m 20s
call-suite-core / call-ci-misc / Code Style
call-suite-core  /  ...  /  C++ Build Warnings
3m 32s
call-suite-core / call-ci-misc / C++ Build Warnings
call-suite-core  /  ...  /  Project Generation
10m 36s
call-suite-core / call-ci-misc / Project Generation
issue-on-error  /  Error Trap
5s
issue-on-error / Error Trap
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
call-suite-core / call-ci-bazel / Bazel
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
call-suite-core / call-ci-bazel / Bazel
Process completed with exit code 1.
call-suite-core / call-ci-bazel / Bazel
Error: ScriptExecutorError when trying to execute: "Error: Job failed with exit code 3."
call-suite-core / call-ci-misc / Project Generation
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazel-contrib/setup-bazel@0.18.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/