When a test hands on a real board there is no way on the console to obtain
any information about why it hung.
With sandbox we can actually find out that it died and get a signal or
exit code. Add this to make it easier to figure out what happened.
So instead of:
test/py/u_boot_spawn.py:171: in expect
c = os.read(self.fd, 1024).decode(errors='replace')
E OSError: [Errno 5] Input/output error
We get:
test/py/u_boot_spawn.py:171: in expect
c = os.read(self.fd, 1024).decode(errors='replace')
E ValueError: U-Boot exited with signal 11 (Signals.SIGSEGV)
Signed-off-by: Simon Glass <sjg@chromium.org>
|
||
|---|---|---|
| .. | ||
| tests | ||
| .gitignore | ||
| conftest.py | ||
| multiplexed_log.css | ||
| multiplexed_log.py | ||
| pytest.ini | ||
| requirements.txt | ||
| test.py | ||
| u_boot_console_base.py | ||
| u_boot_console_exec_attach.py | ||
| u_boot_console_sandbox.py | ||
| u_boot_spawn.py | ||
| u_boot_utils.py | ||