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/D412
Reviewed-by: xclaesse

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

- verify that every D-Bus system service is a systemd system service
  (test for T283)
- verify that every D-Bus session service is a systemd user service
  (test for T284; failures are currently marked as expected)
- verify that every D-Bus service can be activated successfully
  (certain failures are currently marked as expected, with bugs opened)
- verify that a non-systemd-activated D-Bus service cannot be activated
  (marked as an expected failure until T282 is completed)

Differential Revision: https://phabricator.apertis.org/D361
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