ci(qemu): dump per-task bitbake logs on failure#9
Merged
Conversation
The Surface test results step only looked at testimage's oeqa output, which doesn't exist when the build itself fails. Add a Show per-task logs step (gated on if: failure()) that dumps every tmp/work/.../temp/log.do_* file bitbake touched during the build. That's where tar's actual stderr lives, which we currently can't see -- and we've now had two runs of vscode do_unpack failing with 'tar return value 2' in 20ms with no further info.
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.
Two qemu-runtime runs have died at vscode do_unpack with 'tar return value 2' in 20ms and no other context. The actual tar stderr lives in tmp/work//vscode//temp/log.do_unpack. but the Surface test results step only looked at oeqa logs. Add a failure-only step that tails every per-task log bitbake touched, so the next dispatch shows what tar is actually complaining about.