Xavier Claessens authored 9 years ago and Sjoerd Simons committed 9 years ago

Differential Revision: https://phabricator.apertis.org/D532

Philip Withnall authored 9 years ago and Sjoerd Simons committed 9 years ago

On an i.MX6, this test can take around 15 minutes under normal
conditions, so any network delays are going to tip it over the edge and
cause test failures due to timeouts.

Double the timeout to 30 minutes to hopefully avoid this.

Bug: https://bugs.apertis.org/show_bug.cgi?id=476


Signed-off-by: Philip Withnall <philip.withnall@collabora.co.uk>
Reviewed-by: Luis Araujo <luis.araujo@collabora.com>
Differential Revision: https://phabricator.apertis.org/D429

Simon McVittie authored 9 years ago and Sjoerd Simons committed 9 years ago

Differential Revision: https://phabricator.apertis.org/D411
Reviewed-by: xclaesse

Simon McVittie authored 9 years ago and Sjoerd Simons committed 9 years ago

`lava-test-case --shell` waits for LAVA_ACK from the dispatcher after
each of these[1], but run-test-in-systemd does not. This is a point of
incompatibility that could potentially cause or exacerbate issues in
LAVA's "screen-scraping" on the serial console, such as
<https://bugs.apertis.org/show_bug.cgi?id=396>.

[1] https://git.linaro.org/lava/lava-dispatcher.git/blob/HEAD:/lava_dispatcher/lava_test_shell/lava-test-case

Differential Revision: https://phabricator.apertis.org/D388
Reviewed-by: araujo

Xavier Claessens authored 9 years ago and Sjoerd Simons committed 9 years ago

Summary:
This is mostly a 1-1 translation. Tests are not smarter than
what they were before, to the exception that they don't include
sleep() of arbitrary duration everywhere.

Reviewers: smcv, pwith

Differential Revision: https://phabricator.apertis.org/D377

Simon McVittie authored 9 years ago and Sjoerd Simons committed 9 years ago

This is good for usability, and might also prevent it from detecting
inactivity and killing our tests, which upstream developer Neil Williams
warned me might happen (although I haven't seen it on our installation).

Differential Revision: https://phabricator.apertis.org/D372
Reviewed-by: pwith

Simon McVittie authored 9 years ago and Sjoerd Simons committed 9 years ago

D-Bus is a fairly major piece of Apertis infrastructure, so it seems
worth splitting out.

Also rename dbus.yaml (the upstream installed-tests) to
installed-tests.yaml, in preparation for adding other D-Bus tests.

Differential Revision: https://phabricator.apertis.org/D358
Reviewed-by: pwith

Simon McVittie authored 9 years ago and Sjoerd Simons committed 9 years ago

In many tests, we run a scenario twice, once with a fake "malicious"
LD_PRELOAD and one without. Prefix the tests so we get

normal_test1: pass
normal_test2: pass
normal.expected_underlying_tests: pass
normal.expected: pass
malicious_test1: fail
malicious_test2: pass
malicious.expected_underlying_tests: fail
malicious.expected: pass

instead of having "duplicate" results for the underlying tests:

test1: pass
test2: pass
normal.expected_underlying_tests: pass
normal.expected: pass
test1: fail
test2: pass
malicious.expected_underlying_tests: fail
malicious.expected: pass

Differential Revision: https://phabricator.apertis.org/D282


Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Reviewed-by: xclaesse