ci: test forky in test-on-pr.yml workflow - #579
Draft
Christopher Obbard (obbardc) wants to merge 2 commits into
Draft
ci: test forky in test-on-pr.yml workflow#579Christopher Obbard (obbardc) wants to merge 2 commits into
Christopher Obbard (obbardc) wants to merge 2 commits into
Conversation
`Build on PR` builds images for both trixie and forky, but only trixie was ever booted on the boards. Run the LAVA tests over both suites, like build-debian.yml and linux.yml already do. Both builds are published to the same URL, with the suite as a filename prefix, so the build URL retrieved from the build workflow covers both and only the suite passed to lava-test.yml changes. The publish job still only reports the trixie results; the next commit extends it to both suites. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
The publish job downloaded only the trixie artifacts and listed all LAVA jobs in a single flat list, so the forky results were dropped from the check run and the PR comment. Widen the download patterns to every suite of this run attempt and group the job list in the PR comment under a heading per suite, so that the same board tested on trixie and on forky can be told apart. Signed-off-by: Christopher Obbard <chris.obbard@oss.qualcomm.com>
Christopher Obbard (obbardc)
force-pushed
the
wip/obbardc/forky-pr-workflow
branch
from
August 15, 2026 01:14
de9f82a to
c701daf
Compare
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.
Build on PRbuilds images for both trixie and forky, but onlytrixie was ever booted on the boards. Run the LAVA tests over both
suites, like build-debian.yml and linux.yml already do.
Both builds are published to the same URL, with the suite as a
filename prefix, so the build URL retrieved from the build workflow
covers both and only the suite passed to lava-test.yml changes.
The publish job still only reports the trixie results; the next
commit extends it to both suites.
This is a follow-up from #385
Verification
None yet...
workflow_runtriggered workflows always execute the version of the file on the repo's default branch. Sotest-on-pr.ymlon a PR branch can't be ran against the "new" workflow changes.see sample workflow: https://github.com/qualcomm-linux/qcom-deb-images/actions/runs/31854327928