Repository navigation
Conversation
Swap only the astemes_lib_lunit_cli entry (and its spec/icon) in the committed VIPC; every other package is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jki_rsc_toolkits_palette-1.1-1 was installed as @1.1, which VIPM rejects (only 1.1-1 exists), failing the Linux source worker build. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LabVIEWCLI starts LabVIEW as a child that inherits stdout/stderr and keeps running after LabVIEWCLI returns, so piping into tee never reached EOF and the Linux unit-test step hung after 'LUnit operation succeeded.'. Write the output to a file instead and print it once the call returns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dashboard caller read source.ref from .github/labview-ci.yml but checked the tooling out from a repository fixed at install time (the catalog's canonical repo). Repointing source to a fork and one of its branches therefore fetched the fork's branch from the canonical repo and failed. Read source.repo as well, in the thin and consumer callers generated by install.py and in the source repo's own dashboard-pages.yml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gvt367dUuHv3ZsYvywqQ1u
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Runs LUnit unit tests in the Linux worker.
.github/labview/run-unit-tests.sh, the Linux counterpart ofrun-unit-tests.ps1: the sameunitTestsconfig, the same LUnit command template and tokens, the samelunit-<n>.xml/_tooling.jsonoutputs, and it always exits 0 (pass/fail comes from the JUnit file). The frameworks it can run are listed inLINUX_TOOLS; LUnit is the only entry. Any other enabled tool is skipped, and the Linux report says it was not run on Linux.unit-tests-linux-container.yml(ubuntu-latest, same triggers and image selection as the other Linux activities). It deploys tounit-tests/<sha>/linux/and postsCI / Unit Tests (Linux), which the report's platform toggle and the dashboard's Windows / Linux pill already read. The dashboard's Run button now covers Linux too.unit-testsnow supports["windows", "linux"], with the Linux files listed and a GitLabunit-tests-linux.ymltemplate;validate-catalog-source-sync.pypasses. A Windows-only install gets nothing new.ci-tooling.vipcbakes LUnit CLI 1.7.1.32, the first release that runs on Linux. Only that entry changed; every other package in the committed VIPC is untouched.install-vipc-linux.shdropped a package's revision suffix (jki_rsc_toolkits_palette-1.1-1was installed as@1.1, which VIPM rejects). That broke the Linux worker build as soon as the VIPC was applied.documentation.html(both copies), the Unit Testing page, the README row,config.example.yml, and a release-note fragment.After merge
Linux client repos copy the shared Linux worker (
LCWC_LINUX_BASE_IMAGE) instead of bakingci-tooling.vipcthemselves. Run "Build LabVIEW CI Image - Linux" on this repo after merging so the shared worker gets LUnit CLI 1.7.1.32; until then, Linux clients report missing LUnit tooling.Test plan
astemes_lib_lunit_cli v1.7.1.32.os: [windows, linux]in a test repo with an LUnit Test Case:CI / Unit Tests (Linux)= 1 passed, and the report published underunit-tests/<sha>/linux/(results.json: platformlinux, toollunit, 1/1).LabVIEWCLI: passing report, the -350053 missing-tooling banner, a non-LUnit tool skipped as not run on Linux, the-Headlessoverride warning, and no hang when a child process keeps running.install.py --dry-runfor windows / linux / both and for GitLab linux;validate-catalog-source-sync.pypasses.