You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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.
I could provide a little trick to reproduce this issue. Start with
make PLAT=stm32p103 check
and consecutively pressx
followed byctrl + a
. You would find out there's no failure.The text was updated successfully, but these errors were encountered: