Run two more test-info tasks alongside the existing fission task, on mozilla-central only.
There are many possible test-info reports; these are the most obvious:
- a list and summary of all tests, broken out by component
- a list and summary of tests skipped or marked failing on each OS, broken out by component
- a list of all the manifest annotations
I think this will provide a good starting point for discussion around what types of reports
we want to see in the future.
Differential Revision: https://phabricator.services.mozilla.com/D53226
--HG--
extra : moz-landing-system : lando
In bug 1596368 we will adjust them, after disabling tests in coverage debug builds.
Depends on D53000
Differential Revision: https://phabricator.services.mozilla.com/D53001
--HG--
extra : moz-landing-system : lando
We need this for "full" C++17 support (everything is supported, but some
C++17 features still have bugs) and this change also brings Linux into
parity with our Mac requirements.
MANUAL PUSH: build toolchains on inbound to avoid clogging autoland
Differential Revision: https://phabricator.services.mozilla.com/D51450
Upgrade the emulator used by xpcshell tests to 29.2.1, the same version used
by all other android tests.
We have delayed this upgrade because of intermittent failures seen on the new
emulator not seen previously - bug 1568063. After the packet.net upgrade to
Ubuntu 18.04, try runs with the new emulator show that bug 1568063 persists
but has less impact than the intermittent failures it resolves: More tests
pass consistently with the new emulator than with the old.
Differential Revision: https://phabricator.services.mozilla.com/D52851
--HG--
extra : moz-landing-system : lando
This bug disables vismet for browsertime until the png/artifact issues are resolved.
Differential Revision: https://phabricator.services.mozilla.com/D52837
--HG--
extra : moz-landing-system : lando
When we start compiling things to wasm during the build process, we're
going to need a basic sysroot. This new job builds just such a sysroot.
Differential Revision: https://phabricator.services.mozilla.com/D50993
--HG--
extra : moz-landing-system : lando
When these land for Thunderbird, I set the keyword to prevent a build manually.
periodic_file_updates.sh supports that with "-d", but the runme.sh wrapper
does not have a mechanism to set it.
This patch follows the environment variable precedent used for the other
script parameters.
Differential Revision: https://phabricator.services.mozilla.com/D52024
--HG--
extra : moz-landing-system : lando
This patch adds more cold page load tests to browsertime running on integration. Specifically, the following pages will now be tested:
TP6-24: Wikipedia
TP6-17: Yahoo News
TP6-11: Bing
TP6-7: Google Slides
TP6-4: Youtube
TP6-3: Google
TP6-2: Facebook
Differential Revision: https://phabricator.services.mozilla.com/D52011
--HG--
extra : moz-landing-system : lando
The bitbar workers do not support taskcluster-proxy, and so tooltool internal downloads
don't work, even though they had been requested.
Differential Revision: https://phabricator.services.mozilla.com//D52480
--HG--
extra : amend_source : f4ad4bec75b30da67d6769cceedb70a7957cb638
generic-worker uses localhost:8080 for the taskcluster proxy. Many jobs,
including raptor also try to use that port. Disable using the proxy
when only public tooltool downloads were requested, since this
was how thing were configured before.
Differential Revision: https://phabricator.services.mozilla.com//D52478
--HG--
extra : amend_source : 375cb2d84a2dcfbb821f18e4858d86f07db0539b
MANUAL PUSH: Initial push to test new firefox-ci taskcluster cluster.
Differential Revision: https://phabricator.services.mozilla.com/D52453
--HG--
extra : histedit_source : 4bcac76e95d5566db7bb892d44830c03a615f78f
Add new test platforms "android-em-7.0-x86_64-qr/opt" and
"android-em-7.0-x86_64-qr/debug", which run a new test-set
"android-x86_64-qr-tests", which includes reftests and crashtests.
Differential Revision: https://phabricator.services.mozilla.com/D51295
--HG--
extra : moz-landing-system : lando
This also moves the 'mach' docs from /python/mach to /mach. The reason being
that 'mach' doesn't really have anything to do with Python other than its
implemented in it.
Differential Revision: https://phabricator.services.mozilla.com/D52253
--HG--
extra : moz-landing-system : lando
This worker-type isn't working with worker-manager, so backout the change
switching to it.
MANUAL PUSH: Prepration for testing firefox-ci cluster in advance of TCW
Differential Revision: https://phabricator.services.mozilla.com/D52119
--HG--
extra : histedit_source : 4f2689d47f25864b87abae6eeb55cc09936f4a61
We originally had a different plan related to migrating worker-types to a new cluster.
Remove the code that supported that.
Differential Revision: https://phabricator.services.mozilla.com/D52076
--HG--
extra : rebase_source : 1c0945e96add41659f56013a01d4d246e2d69dd3
extra : histedit_source : 03acebc1cc6796bd60cd472bc3c5c92a9c17f02b
MANUAL PUSH: (a) This patch will cause a ton of toolchain rebuilds, and might as well do that on central right now rather than autoland, and (b) We want to test the new Taskcluster instance today, and will be testing THAT on m-c, so we'll need this patch on m-c before we can test the new cluster as well.
tooltool at present needs to support production (legacy cluster) but its auth system is tied to that cluster.
Which means that using tooltool in the new cluster ahead of TCW is harder. We have swapped the credentials for the tooltool staging deployment to use the new tc cluster, so when we're using the taskcluster proxy we need to have it swap between legacy and new tooltool url's depending on which cluster (ROOT_URL) we're using.
This patch is intended to be ok to land on production code today, and could be backed out after the TCW when production tooltool will be configured to work with the firefox-ci cluster itself.
Differential Revision: https://phabricator.services.mozilla.com/D52089