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

Terminal blocked after cargo test #338

Closed
asensio-project opened this issue Jan 27, 2023 · 3 comments · Fixed by #339
Closed

Terminal blocked after cargo test #338

asensio-project opened this issue Jan 27, 2023 · 3 comments · Fixed by #339

Comments

@asensio-project
Copy link
Contributor

Hello,

After I execute cargo test the STDOUT of my terminal blocks, so I cannot see what I am writing. This happens after #333. I think that it's an unclosed pipe in the run_qemu() function, but I don't know anything more.

I am working for fixing it. And I will publish a PR. But if someone knows something...

Thanks!

@phil-opp
Copy link
Member

You mean while cargo test runs? Or still afterwards?

In case you mean the former: that's probably because we're forwarding stdin to QEMU. Let me try to fix this.

@phil-opp
Copy link
Member

I opened #339 to set stdin to null for the QEMU command. Could you try whether this fixes your issue?

@asensio-project
Copy link
Contributor Author

I tried it, and it fixes it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants