Skip to content
CI

[IN] Fixing support for IR, adding gcctestsuite to improve coverage #24

Sign in to view logs

[IN] Fixing support for IR, adding gcctestsuite to improve coverage

[IN] Fixing support for IR, adding gcctestsuite to improve coverage #24

Triggered via pull request March 22, 2026 14:05
@matglamatgla
synchronize #6
gccTests
Status Failure
Total duration 2m 8s
Artifacts –

ci.yml

on: pull_request
build-and-test
2m 3s
build-and-test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
build-and-test
The process '/usr/bin/git' failed with exit code 128
build-and-test
Fetched in submodule path 'tests/ir_tests/qemu/mps2-an505/libs/newlib', but it did not contain ede095ca4ff4c9d2640dd85187d51b86b8cb4c65. Direct fetching of that commit failed.
build-and-test
remote error: upload-pack: not our ref ede095ca4ff4c9d2640dd85187d51b86b8cb4c65
build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/