marionette-harness is implemented as a "generic" task and
can be triggered with the following try syntax:
`-p linux64_tc -j marionette-harness -u none -t none`
The Marionette harness tests do not depend on a browser build,
they only exercise Python code.
Add option to testing/docker/desktop-build/bin/build.sh to
execute any in-tree script instead of only `build-linux.sh`.
This feature is used to call
testing/taskcluster/scripts/tester/harness-test-linux.sh, which
in turn executes the mozharness script specified in the environment.
MozReview-Commit-ID: H08v8ow4p8q
For Linux64 debug test jobs running on TaskCluster we have been using gnome-session, however,
this differs from how we run things on the Buildbot AMIs where we use xsession instead.
This does not add many changes on test results but mainly help us have a closer set-up to
Buildbot's and possibly have a better VNC experience (jmaher reported some issues with gnome-session).
For Linux64 debug test jobs running on TaskCluster we have been using gnome-session, however,
this differs from how we run things on the Buildbot AMIs where we use xsession instead.
This does not add many changes on test results but mainly help us have a closer set-up to
Buildbot's and possibly have a better VNC experience (jmaher reported some issues with gnome-session).
For jobs requiring a window manager for the desktop-image, disable the screen saver and prevent
it from locking the screen.
This solves an immense number of test failures which were causing long run times (2-3x) and test timeouts.
This adds test configs for desktop linux64 unittests, including: mochitest-plain,
mochitest-browser-chrome, mochitest-devtools-chrome, reftest and xpcshell. It
also does a minor refactor of the b2g configs to remove some b2g-specific logic
from the base 'test.yml' config.
This does *not* schedule these tests anywhere just yet.
This adds test configs for desktop linux64 unittests, including: mochitest-plain,
mochitest-browser-chrome, mochitest-devtools-chrome, reftest and xpcshell. It
also does a minor refactor of the b2g configs to remove some b2g-specific logic
from the base 'test.yml' config.
This does *not* schedule these tests anywhere just yet.
This generally makes the approach look more like that for desktop-build. The
major difference is that `bin/test.sh` takes arguments which are passed on to
the mzoharness script (MOZHARNESS_SCRIPT) with the addition of config
arguments (MOZHARNESS_CONFIG)
