Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Twister does not capture stdout or stderr from qemu launch #72997

Open
kuikka opened this issue May 19, 2024 · 0 comments · May be fixed by #72998
Open

Twister does not capture stdout or stderr from qemu launch #72997

kuikka opened this issue May 19, 2024 · 0 comments · May be fixed by #72998
Assignees
Labels
area: Twister Twister Enhancement Changes/Updates/Additions to existing features

Comments

@kuikka
Copy link

kuikka commented May 19, 2024

Describe the bug
The current QemuHandler in twister does not capture stdout or stderr from the qemu launch (really "ninja run" usually). This makes debugging qemu issues difficult.

To Reproduce
Steps to reproduce the behavior:

  • Run tests using twister where the required qemu is not installed on the system.
  • There are no logs from the qemu launch to indicate what went wrong.

Expected behavior
Qemu stdout and stderr are logged along "handler.log" during test execution.

Impact
Annoyance when failures happen in CI and there are no logs.

I will attach a diff that changes this behavior but given that I'm no expert in twister, I'm happy to revise as neede.

@kuikka kuikka added the bug The issue is a bug, or the PR is fixing a bug label May 19, 2024
@kuikka kuikka linked a pull request May 19, 2024 that will close this issue
@nashif nashif added Enhancement Changes/Updates/Additions to existing features and removed bug The issue is a bug, or the PR is fixing a bug labels May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Twister Twister Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants