Repository navigation
REQ 035
REQ-035: Linux LUnit feasibility spike (ADR-0003 Phase 2) -- investigative; outcome (a) feasible/satisfies REQ-036 pre-condition, (b) documented blocker, not release-gating either way
A disposable Linux LUnit feasibility spike shall determine, before Linux becomes release-gating, whether the LUnit/LUnit CLI VI packages and LabVIEWCLI's LUnit operation can run unattended (including any headless-display/Xvfb requirement) against this engine's pinned-by-digest nationalinstruments/labview Linux container image on a GitHub-hosted Linux runner.
No upstream reference implementation exists for Linux; per ADR-0003, this engine must independently determine feasibility rather than assume Windows's mechanism transfers unchanged.
Resolved: outcome (a), feasible (per ADR-0003's Phase-2 Addendum) -- confirmed via direct local Docker testing (Linux containers run natively on this engine's own build host) before CI: LabVIEWCLI's LUnit operation runs to completion with no externally-provided DISPLAY/Xvfb setup needed -- LabVIEW itself spawns its own internal Xvfb :99 virtual framebuffer when none is provided, confirmed via a direct process-tree inspection (#94's independent verification review, which corrected this row's earlier "no virtual framebuffer at all" overclaim). No NSIS-equivalent installer is needed (neither of the two Windows-container-specific bugs that required one apply to Linux). Two additional Linux-specific named test failures were found and confirmed (see REQ-036), beyond the Windows-shared waiver.
Verified (live, fork + upstream): confirmed feasible via direct local Docker testing, then real workflow_dispatch runs on both the fork (run 42372457595) and upstream VITechnologies/projectbuddy (run 42372700928, after #92 merged) -- identical results. See ADR-0003's Phase-2 Addendum.
Software-Requirements-Specification
High
Not yet implemented
No upstream reference; net-new spike, tracked in #87
Planned