test(ci): smoke-test premerge distro validation (fork) - #97
Open
Bjordis Collaku (bjordiscollaku) wants to merge 1 commit into
Conversation
…fork) Exercises the canonical-premerge distro validation chain for a fork-originated pull request, after the pkg-linux-qcom-canonical#95 identity resolution fix. No source changes; this commit is intentionally empty. Signed-off-by: Bjordis Collaku <bcollaku@qti.qualcomm.com>
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.
Fork smoke test for the canonical-premerge distro validation chain,
opened fresh off the current
resolute-qcom-develtip to avoid themerge conflicts and staleness that affected the earlier smoke PRs
(#82, #90).
Exercises the fix in #95
for the fork case: once the premerge kernel build succeeds, the
workflow_runorchestrator should resolve this fork PR's identitycorrectly and dispatch distro image validation, which is exactly the
scenario that previously failed on #90.
No source changes; the commit is intentionally empty.