ci(debusine): read workspace from $GITHUB_OUTPUT, not a stale output file - #59
Merged
Bjordis Collaku (bjordiscollaku) merged 1 commit intoJul 23, 2026
Conversation
…file debusine-action PR #62 (build-failure-logs) changed lib/build to write workspace and workflow_id directly to $GITHUB_OUTPUT before polling, so that these values survive a poll failure. It removed the separate 'output' file that lib/build previously created as its sole output artifact. The Build in Debusine step here still expected that removed file: it ran 'cat output >> "$GITHUB_OUTPUT"' and then read 'output' again to derive workspace_url. Since debusine-action/main now never creates 'output', the 'cat' fails with 'No such file or directory' and the step exits 1 even though the underlying Debusine build succeeded. This has failed every 'trixie' leg of the daily build since debusine- action#62 merged on 2026-07-16. Read the workspace value back out of $GITHUB_OUTPUT instead of the removed file, matching how debusine-action's own reusable workflow (.github/workflows/debusine.yml) already consumes lib/build's outputs. Signed-off-by: Bjordis Collaku <bcollaku@qti.qualcomm.com>
Robie Basak (basak-qcom)
approved these changes
Jul 23, 2026
Bjordis Collaku (bjordiscollaku)
merged commit Jul 23, 2026
08cb492
into
main
18 of 19 checks passed
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
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
Every daily
trixiebuild has failed since debusine-action PR #62 (build-failure-logs) merged on 2026-07-16. This restores the daily pipeline to green by adaptingbuild-kernel-debusine.ymlto the newlib/buildoutput contract.Root cause
debusine-actionPR #62 changedlib/buildto emitworkspaceandworkflow_iddirectly to$GITHUB_OUTPUTbefore polling Debusine, so those values survive a poll failure. As part of that change,lib/buildstopped writing the separateoutputfile it used to produce as its sole output artifact.Our
Build in Debusinestep inbuild-kernel-debusine.ymlstill assumed that removed file:Since
debusine-action@mainno longer createsoutput,cat outputfails withNo such file or directory, and the step exits 1 even though the underlying Debusine build itself completed successfully. This has failed everytrixieleg ofdaily.ymlsince 2026-07-16 (see runs 29541747691 through 29876594727).Fix
Read the
workspacevalue directly from$GITHUB_OUTPUT, whichlib/buildnow populates itself, instead of the removedoutputfile. This matches howdebusine-action's own reusable workflow (.github/workflows/debusine.yml) already consumeslib/build's outputs.Validation
Ran
build-kernel-deb.ymlend to end on this branch againsttrixie:run 29946314673
Build (Debusine)(previously the failing job): success, 26m30sPublish Debusine artifacts: success, 57s