test: capture the QEMU client serial console on failure#2943
Open
pasinskim wants to merge 1 commit into
Open
Conversation
The failure teardown only prints device output over SSH, which is empty when the device is unreachable -- which is exactly the "Device never rebooted" failure mode (a hung guest reset). Capture the client's serial console via "docker compose logs" (which works without SSH) into the per-test logs, so the guest's actual reboot behaviour (e.g. "reboot: machine restart" followed by silence) is visible directly in CI artifacts. Changelog: None Signed-off-by: pasinskim <marcin.pasinski@northern.tech>
Contributor
|
@pasinskim, start a full integration test pipeline with:
my commands and optionsYou can prevent me from automatically starting CI pipelines:
You can trigger a client pipeline on multiple prs with:
You can trigger a client pipeline for a specific Mender Client release with:
You can trigger GitHub->GitLab branch sync with:
You can print PR statistics for a repository with:
You can deploy a review app with:
You can run e2e tests against a deployed review app with:
You can cherry pick to a given branch or branches with:
|
Member
Author
|
@mender-test-bot start integration pipeline |
Contributor
|
Hello 😺 I created a pipeline for you here: Pipeline-2646022290 Build Configuration Matrix
|
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.
The failure teardown only prints device output over SSH, which is empty when the device is unreachable -- which is exactly the "Device never rebooted" failure mode (a hung guest reset). Capture the client's serial console via "docker compose logs" (which works without SSH) into the per-test logs, so the guest's actual reboot behaviour (e.g. "reboot: machine restart" followed by silence) is visible directly in CI artifacts.
Changelog: None