history
Traceable and base-MATLAB CI validation
id: LK-20260713-traceable-base-matlab-ci
date: 2026-07-13
sequence: 51
type: ci
compatibility: compatible
scope: GitHub Actions and MATLAB validation routing
Context
CI failures and stalls could end without enough information to identify the active test, and ordinary success on a toolbox-rich development machine did not prove that base-MATLAB users could run representative workflows.
Decision and rationale
Make the existing official runner publish progress and active-test state, and add a distinct compatibility gate that combines static calls, product ownership, and toolbox-shadowed behavior.
Changes
- Added per-test progress, heartbeat, active-test, timeout-summary, and artifact publication behavior to CI.
- Added
buildtool baseMatlaband representative toolbox-shadow workflows. - Improved changed-file routing to target direct consumers while retaining explicit owners such as the launcher GUI suite.
- Corrected result aggregation so assumption-filtered tests remain visible as skipped without being misreported as shard failures.
User and data impact
Base-MATLAB compatibility is now an explicit supported path, and failed or stalled CI runs provide enough state to identify the last active test. Runtime scientific outputs are not changed by this record.
Compatibility and migration
Existing build tasks remain available. Maintainers can add baseMatlab to local validation without installing or uninstalling toolboxes.
Validation
CI policy, build-task framework, changed-routing, toolbox dependency, and representative workflow tests guard the new behavior.
Evidence
The command matrix is in docs/development/maintain-and-release/testing.md; CI uploads official runner logs and active-test artifacts. Commit 28ff8edb made MATLAB failures traceable, 37bd7fd5 enforced Base MATLAB compatibility, and 2c9b8792 preserved launcher validation ownership.
Known limitations and follow-up
Shadow tests cover known dependency risks and cannot simulate every licensed toolbox combination; MATLAB product-ownership analysis remains the broad check.