-
Notifications
You must be signed in to change notification settings - Fork 299
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
test_env.sh: output kernel console to stdout #944
Conversation
Doesn't seem to work with qemu in |
Strange, it worked locally, I'll test again. |
@eugeneia I can't reproduce this using Nix toolchain on
I'll close the PR and reopen, hopefully that will retrigger SnabbBot build. |
I've tested also with qemu 2.4.1, @eugeneia if you find some time to test this locally I'd appreciate it :) |
I can't reproduce it either. Reopening does not trigger a SnabbBot build (only new commits), did that now manually. Edit: for the record, the failure we are talking about is here https://gist.github.com/SnabbBot/3447fc270c52b233ce438a39b9a11b5f |
I can reproduce it on davos, seems to be a QEMU bug that is triggered here? Here is the qemu logs:
|
@eugeneia could you try different qemu version? It does clearly hint to be a qemu bug. I could try 1.4.0 and see if I can reproduce. |
@domenkozar The bug isn't triggered in QEMU v2.4.1, I opened #948 to avoid this issue. |
Thanks! |
@eugeneia now it passes! |
Implement alarm summary
Once we start using Nix fixtures, guest processes output will be also part of console output so it will be easier to see what's going on inside the guest.
cc @eugeneia