diff options
author | Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com> | 2025-10-07 19:38:06 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-10-09 10:58:07 +0100 |
commit | 8810c1deb029f1d8dba915c39f7aae92e9e9f2ad (patch) | |
tree | cc6d7be5b9a1c6aab40e723a7545a411cbb7ddc0 /meta/packages/qemu/qemu-git/qemu-add-gl-host-code.patch | |
parent | abd46facfa5a214d4895d368707681172e1624e6 (diff) | |
download | poky-8810c1deb029f1d8dba915c39f7aae92e9e9f2ad.tar.gz |
oeqa: target: ssh: Fail on SSH error even when errors are ignored
Most tests running SSH commands ask for no error to be raised when the
returned status is not 0. As run() will return this status, they may
later use its value to do a similar check on their own, or completely
ignore it. But most of the tests do not check if the non-zero status is
caused by a fail of the command run on the target or by a fail of SSH
itself.
This can lead to confusion when the error does not come from the command
executed on the target but from SSH itself: test might wrongfully be
marked as PASSED or might fail with incoherent errors.
As SSH errors are always reported with exit code 255, we can easily
filter these.
Modify OESSHTarget.run() behaviour so an AssertionError is raised on SSH
failures, even when ignore_status parameter is True. Still allow to
explicitly ignore this error for the rare cases where this can be
needed.
(From OE-Core rev: afe118d4f2de1f636b3a81dc692da35b35a3f2d7)
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/packages/qemu/qemu-git/qemu-add-gl-host-code.patch')
0 files changed, 0 insertions, 0 deletions