Troubleshooting
Setup issues
- Ensure NI LabVIEW and g-cli are installed and accessible.
- Verify PowerShell 7+ (
pwsh) is available on the PATH.
- Confirm the working directory and file paths are correct.
Missing dependencies
- Check that required packages and toolkits are installed.
- Install any missing modules or scripts referenced by the action.
- Review action parameters for typos that could hide dependencies.
Interpreting exit codes
0 indicates success; any non-zero code signals a failure.- Consult each action’s documentation for specific return codes.
- Use verbose logs to pinpoint the cause of unexpected codes.
Missing g-cli or LabVIEW
Symptom: Actions fail immediately because g-cli or LabVIEW is absent or misconfigured.
Example error output
❌ g-cli executable not found in PATH.
Invoke-OSAction.ps1 : g-cli: command not found
Resolution
- Install NI LabVIEW and g-cli.
- If g-cli isn’t on
PATH, provide its location via gcliPath.
- Verify the path uses proper separators and escaping.
32- vs 64-bit mismatches
Symptom: g-cli cannot find the requested LabVIEW architecture.
Example error output
Unsupported VIP_LVVersion or SupportedBitness for VIP_LVVersion_A.
g-cli: could not locate LabVIEW 2021 (64-bit)
Resolution
- Ensure the installed LabVIEW bitness matches the
SupportedBitness argument.
- Confirm action configuration (e.g.,
run-unit-tests) specifies the correct SupportedBitness.
- Use a g-cli build that matches the target architecture.
Permission or working-directory errors
Symptom: Files or directories cannot be accessed.
Example error output
Invoke-OSAction.ps1 : Cannot find path 'C:\\repo\\project' because it does not exist.
Access to the path '/opt/labview/Tooling' is denied.
Resolution
- Verify the working directory is correct or set
-WorkingDirectory.
- Ensure the runner has permission to read/write the necessary paths.