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

Test suites don't expose failed on cases of forced terminating QEMU #49

Open
iankuan opened this issue Oct 15, 2017 · 3 comments
Open

Comments

@iankuan
Copy link
Member

iankuan commented Oct 15, 2017

I could provide a little trick to reproduce this issue. Start with make PLAT=stm32p103 check and consecutively press x followed by ctrl + a. You would find out there's no failure.

@jserv
Copy link
Member

jserv commented Oct 15, 2017

In other words, test runner should manipulate UNIX signals properly. Terminating QEMU is another case, and we don't really be aware of the external actions.

@iankuan iankuan changed the title Test suites don't expose failed on cases of forced termination Test suites don't expose failed on cases of forced terminating QEMU Oct 15, 2017
@iankuan
Copy link
Member Author

iankuan commented Oct 15, 2017

In current runner implementation, it can handle SIGINT well and list test cases which don't execute yet.

In case of QEMU, It's necessary to terminate QEMU due to system halt. However, It would quite often occur on developing a new feature. Take it as a failure rather than pass is good for developers to fix it and also pretty make sense.

@jserv
Copy link
Member

jserv commented Oct 15, 2017

We can utilize semihosting to perform bidirectional verification between host and device(s).

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

No branches or pull requests

2 participants