Skip to content
Core Strict CI

fix(config): preserve explicit config file precedence on reload #163

Sign in to view logs

fix(config): preserve explicit config file precedence on reload

fix(config): preserve explicit config file precedence on reload #163

Re-run triggered July 13, 2026 08:20
@GaspardKiriraGaspardKirira
a427ab7
dev
Status Cancelled
Total duration 35m 20s
Artifacts –

core-strict-ci.yml

on: push
Matrix: sanitized-tests
Runtime Smoke and Shutdown Checks
4m 43s
Runtime Smoke and Shutdown Checks
Static Analysis
7m 12s
Static Analysis
Valgrind Memory Checks
9m 47s
Valgrind Memory Checks
Release and Benchmark Coverage
9m 52s
Release and Benchmark Coverage
Package Export Check
2m 1s
Package Export Check
Core Strict CI Summary
0s
Core Strict CI Summary
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Sanitized Tests (gcc, tls=ON, template=AUTO, ui=AUTO)
The job has exceeded the maximum execution time of 35m0s
Sanitized Tests (gcc, tls=ON, template=AUTO, ui=AUTO)
The operation was canceled.
Sanitized Tests (gcc, tls=ON, template=AUTO, ui=AUTO)
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/