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.
--HG--
extra : commitid : HdWat17LZNb
extra : rebase_source : 456b0261fc06131e22d8d5a37adf12f090abe5bd
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.
--HG--
extra : commitid : 3wjUmgfi1se
extra : rebase_source : 1369d5b3fcfb5e6e351c8384187772dae52f341f
extra : amend_source : 47f9574b013bfb892713a52d9377655eb9040608
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)
--HG--
rename : testing/docker/desktop-build/bin/build.sh => testing/docker/desktop-test/bin/test.sh
rename : testing/docker/desktop-test/mozharness_configs/remove_executables.py => testing/mozharness/remove_executables.py
extra : commitid : GyMeTBpCwm8
extra : rebase_source : 1a61f9bc32066ad6f9fce504d3e8ac67e39b105d
We add to TaskClusterArtifactFinderMixin the ability to support
normal Buildbot Bridge triggered tasks + tasks that contain the
property 'parent_task_id'.
This allows for tasks to depend on tasks different than the one
they're going to grab artifacts from.
In this patch we support both the traditional approach
plus the new model.
We also add support for native TC tasks where properties.json
is not available. With pure TC tasks we assume
['extra']['locations']['build'] being set and pointing to
the installer artifact.
--HG--
extra : commitid : GKcTU68PAoZ
extra : rebase_source : 6f70be2748000bd85995861bee7a54d0a6a5933b
When we added support for finding artifacts from TaskCluster BBB tasks
we added an error for not finding the artifacts either via buildbot properties
or through the TC APIs.
Unfortunately, this error did not take into consideration when mozharness sets
the artifacts through the options --installer-url and --test-url.
We're removing the error as few lines below the error logging is sufficient
to handle all three cases and not raise misleading errors.
--HG--
extra : commitid : 1nxRrdDWutr
extra : histedit_source : b0720a9783cea7cdde9866fd09d5d8847c9c08e3
