We don't test all our example executables run successfully

[Alan Griffiths]

device-runtests-mir-test has:

export test_suites="mir_performance_tests mir_unit_tests mir_umock_unit_tests mir_integration_tests mir_acceptance_tests mir_umock_acceptance_tests mir_demo_client_basic mir_demo_client_fingerpaint mir_demo_client_eglplasma mir_demo_client_multiwin mir_demo_client_egltriangle mir_privileged_tests mir_android_diagnostics"

Only the mir_demo_client_XXX binaries explicitly listed here are run.

We ought to ensure *all* the clients get run. Not just a random selection.

I came across this because of a problem with mir_demo_client_flicker (c.f. lp:~alan-griffiths/mir/tidy-code/+merge/288629 and lp:1555620) but it applies to all the shipped binaries missing from the above list.

[Alan Griffiths (alan-griffiths)]

Also, there are other demo binaries we ship that we ought to test. (And some diagnostic ones.)

[Alan Griffiths (alan-griffiths)]

I guess something like:

    export test_suites="`dpkg-query -L mir-demos | grep mir_demo_client_ | sed s_/usr/bin/__`"

will cover running all the clients.

FWIW I got a few failures to investigate tomorrow with:

    $ for test in `dpkg-query -L mir-demos | grep mir_demo_client_ | sed s_/usr/bin/__`; do mir_demo_server --test-timeout 3 --test-client $test ; done

[Daniel van Vugt (vanvugt)]

Originally, this was intentional. But if you want to address it, that's OK too.

[Michał Sawicz (saviq)]

Syncing task from Mir.