Skip to content

tests: Also output return value of test client, in case of an error

Quoting both commit messages here:

There is no reason to wait for the client twice just to check the return
value of the subprocess.
Instead, directly compare the return value.
If the test client does not fail internally, but an unexpected return
value of the subprocess is returned, it is useful to know what value was
returned in order to be able to investigate the issue.

@3v1n0 Could you run the arm64 test in https://launchpadlibrarian.net/672612234/buildlog_ubuntu-mantic-arm64.gnome-remote-desktop_44.2-2.5_BUILDING.txt.gz again with this MR applied?
In that test, the test in the test client succeeds, but for some reason the test client does not return 0 here. With this MR, we should know see the return value of the test client in case it fails.

Merge request reports