Add Android 7.0 gtests, opt and debug, running against the geckoview
TestRunnerActivity.
Differential Revision: https://phabricator.services.mozilla.com/D27016
--HG--
extra : moz-landing-system : lando
This disables GLES3 in the android emulator unless WebRender is
explicitly enabled, because for now the half-baked ES3 support in the
emulator causes some WebGL tests to fail.
Differential Revision: https://phabricator.services.mozilla.com/D26940
--HG--
extra : moz-landing-system : lando
This only uses cross-platform tools, so switch to running these on linux, which
cuts the runtime down from ~20m to ~3m.
Differential Revision: https://phabricator.services.mozilla.com/D1080
--HG--
extra : moz-landing-system : lando
In automation, the script is run with `mach python`, and all the dependencies
are vendored, so just use them directly.
Differential Revision: https://phabricator.services.mozilla.com/D25839
--HG--
extra : moz-landing-system : lando
These existed for when bouncer was updated via mozharness, and they are unused in bouncer-check.
By removing the paths, we make the configuration easier to read and update.
Differential Revision: https://phabricator.services.mozilla.com/D25838
--HG--
extra : moz-landing-system : lando
Fennec doesn't have a bouncer check task, and bouncer is update via bouncerscript.
Differential Revision: https://phabricator.services.mozilla.com/D25837
--HG--
extra : moz-landing-system : lando
I beleive these entries date from when bouncer config was handled by mozharness
rather than bounerscript and are now obsolete.
Differential Revision: https://phabricator.services.mozilla.com/D25836
--HG--
extra : moz-landing-system : lando
When adding a new platform, the first release will be at the watershed, and
there will be no update paths. Rather than failing in this case (requiring the
update-verify setup happen after the first release), generate an empty config
which will allow the later tasks to turn green.
Differential Revision: https://phabricator.services.mozilla.com/D25833
--HG--
extra : moz-landing-system : lando
These will run on android-hw against the latest reference browser nightly.
Since they are try-only, they can only be scheduled with |mach try fuzzy
--full|.
Differential Revision: https://phabricator.services.mozilla.com/D25801
--HG--
extra : moz-landing-system : lando
The secret with the ssh key already exists in taskcluster, this tells
mozharness to try to access it.
Differential Revision: https://phabricator.services.mozilla.com/D25700
--HG--
extra : moz-landing-system : lando
This functionality has been replaced by beetmover. Also remove `mozharness.mozilla.aws`,
of which this was the only consumer.
Differential Revision: https://phabricator.services.mozilla.com/D25676
--HG--
extra : moz-landing-system : lando
There used to be various values that were substituted into the mozharness
configuration for L10n jobs. All those substitutions have been removed, but the
code to support them is still around. This removes that code.
Differential Revision: https://phabricator.services.mozilla.com/D25143
--HG--
extra : moz-landing-system : lando
An `sy-tp6` variant is added to the AWSY test suite that runs against the tp6 pageset.
Differential Revision: https://phabricator.services.mozilla.com/D24585
--HG--
extra : moz-landing-system : lando
There are a few windows/mac-only suites that were missed since we were only
reading the linux variant.
Depends on D25401
Differential Revision: https://phabricator.services.mozilla.com/D25432
--HG--
extra : moz-landing-system : lando
This also renames win_taskcluster_unittest.py to win_unittest.py for
consistency with the other platforms.
Differential Revision: https://phabricator.services.mozilla.com/D25401
--HG--
extra : moz-landing-system : lando
There used to be various values that were substituted into the mozharness
configuration for L10n jobs. All those substitutions have been removed, but the
code to support them is still around. This removes that code.
Differential Revision: https://phabricator.services.mozilla.com/D25143
--HG--
extra : moz-landing-system : lando
This only uses cross-platform tools, so switch to running these on linux, which
cuts the runtime down from ~20m to ~3m.
Differential Revision: https://phabricator.services.mozilla.com/D1080
--HG--
extra : moz-landing-system : lando
Mozharness appends -chunked/-coverage to some suites, but the build system/test
resolver don't have any concept of these things. We need to normalize these out
for the purposes of MOZHARNESS_TEST_PATHS.
Differential Revision: https://phabricator.services.mozilla.com/D25015
--HG--
extra : moz-landing-system : lando
It turns out bug 1489100 regressed the ability to specify test paths for most
suites by naively assuming that mozharness uses suite names that look like:
<flavor>-<subsuite>
In reality, there is no consistency to how suite names are generated. This test
does a few things:
1) Patches the moztest.TestResolver to return a list of all possible
suites/subsuites (assuming the lists in moztest.resolve are up to date).
2) Finds all the suites defined in the mozharness configs (e.g
linux_unittest.py), and uses these are parametrized inputs.
3) Checks that for each test suite,
DesktopUnittest._get_mozharness_test_paths() returns something.
I've marked all of the test suites that currently fail as expected. This way I
have a good sense of what needs to be fixed, and can validate my changes as I
move through the list.
Differential Revision: https://phabricator.services.mozilla.com/D25014
--HG--
extra : moz-landing-system : lando
We have moved per-branch configuration to taskcluster, so we can remove that
support in mozharness.
Differential Revision: https://phabricator.services.mozilla.com/D24564
--HG--
extra : moz-landing-system : lando
The release mozconfigs set `MOZ_PGO` and all shipping builds set the `nightly`
mozharness config, so we don't need to additionaly set PGO based on the branch.
Differential Revision: https://phabricator.services.mozilla.com/D24563
--HG--
extra : moz-landing-system : lando
The only thing this affects is the default update channel, but for shipping builds, this is set
explicitly via taskcluster, and for other branches, defaults to `default`.
Differential Revision: https://phabricator.services.mozilla.com/D24562
--HG--
extra : moz-landing-system : lando
Taskcluster has authorative information about the repository being built, so
pass that to mozharness, rather than have mozharness reconstruct it from
hand-maintained mozharness config.
Differential Revision: https://phabricator.services.mozilla.com/D24561
--HG--
extra : moz-landing-system : lando
The code that actually downloads it is behind a condition that isn't set
anywhere.
Differential Revision: https://phabricator.services.mozilla.com/D24215
--HG--
extra : moz-landing-system : lando
This introduces a mozharness script, android_emulator_pgo.py, to run the
profileserver suite with the PGO-instrumented Android build, and collect
the profile data and jarlog.
The mozharness script contains some redundancy with
build/pgo/profileserver.py, but the additional requirements for Android
to use adb and existing mozharness classes to control the emulator made
it difficult to share the desktop profileserver implementation.
Differential Revision: https://phabricator.services.mozilla.com/D22825
--HG--
extra : source : c151ebf303cad175e24bcc0965c800a9d12ecb3b
This is the first stage of the Android PGO task pipeline to generate an
instrumented build.
Differential Revision: https://phabricator.services.mozilla.com/D22824
--HG--
extra : source : b96dd954a456d8088a3ceda66f51d4106f516b4a
This introduces a mozharness script, android_emulator_pgo.py, to run the
profileserver suite with the PGO-instrumented Android build, and collect
the profile data and jarlog.
The mozharness script contains some redundancy with
build/pgo/profileserver.py, but the additional requirements for Android
to use adb and existing mozharness classes to control the emulator made
it difficult to share the desktop profileserver implementation.
Differential Revision: https://phabricator.services.mozilla.com/D22825
--HG--
extra : moz-landing-system : lando
This is the first stage of the Android PGO task pipeline to generate an
instrumented build.
Differential Revision: https://phabricator.services.mozilla.com/D22824
--HG--
extra : moz-landing-system : lando
In the mochitest harness, is_fennec is populated by examining harness options, and
is_emulator and android_version are populated by examining the device via mozdevice.
The per-test code doesn't have those options and the emulator may not be available
yet, so I've opted for populated those fields from mozharness configuration. In
practice, we only run Android TV on Android 4.3, where is_fennec=True, is_emulator=True,
and android_version=18. I'd like to run TV on Android 7.0/geckoview eventually,
where is_fennec=False, is_emulator=True, and android_version=24.
Since I was here, I also removed 'stylo' from the per-test mozinfo, since that field
is obsolete now.
Differential Revision: https://phabricator.services.mozilla.com/D23595
--HG--
extra : moz-landing-system : lando
This commit vendors `robustcheckout` from the version-control-tools
repository, revision 8e3bb142dfa9.
Differential Revision: https://phabricator.services.mozilla.com/D23566
--HG--
extra : moz-landing-system : lando
the Canavas debugger tests appear to be the last tests using browser-chrome-gpu. This patch
removes those tests from being run on try.
Differential Revision: https://phabricator.services.mozilla.com/D23314
--HG--
extra : moz-landing-system : lando
Artifact mozconfigs are not necessarily up-to-date wrt changes to the
nightly mozconfigs, and all in all, shouldn't be much different from
them.
It's just better to use the nightly mozconfigs (or beta on beta, etc.)
and make the mozconfigs themselves handle the few things that need to be
different when the USE_ARTIFACT environment is set (which is now
consistently set by taskcluster)
This does have the side effect of turning builds that actually don't
support artifact builds red when using --artifact on try, instead of
having them silently not be artifact builds as currently happens.
Depends on D21314
Differential Revision: https://phabricator.services.mozilla.com/D21315
--HG--
extra : moz-landing-system : lando
While try syntax is approaching its EOL, the fact that using it to do
artifact builds does some things subtly differently from using try
config is not helpful.
Depends on D22055
Differential Revision: https://phabricator.services.mozilla.com/D21312
--HG--
extra : moz-landing-system : lando
This patch moves testing/raptor/raptor/playback into its own testing package in testing/mozbase/mozproxy
so we can use the proxy in other places than Raptor.
Differential Revision: https://phabricator.services.mozilla.com/D21200
--HG--
rename : testing/raptor/raptor/playback/__init__.py => testing/mozbase/mozproxy/mozproxy/__init__.py
rename : testing/raptor/raptor/playback/base.py => testing/mozbase/mozproxy/mozproxy/backends/base.py
rename : testing/raptor/raptor/playback/mitmproxy.py => testing/mozbase/mozproxy/mozproxy/backends/mitm.py
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-linux64.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-linux64.manifest
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-osx.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-osx.manifest
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-win.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-win.manifest
rename : testing/raptor/raptor/playback/mitmproxy_requirements.txt => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy_requirements.txt
extra : moz-landing-system : lando
The existing ANR and tombstone checks in remoteautomation are used
by mochitests and reftests but are awkward for other harnesses like cppunit
that do not use remoteautomation...and easily missed. This patch moves that
code to the mozharness AndroidMixin, treating ANRs and tombstones like the
logcat: Make sure any old logs are deleted when the mozharness script starts,
then move any logs found at the end of the run to the upload directory.
https://treeherder.mozilla.org/#/jobs?repo=try&tier=1%2C2%2C3&revision=f3de1e9836da2b0c9232f5d92c751b979459e19b
demonstrates tombstone artifacts for the Android 7.0 cppunit tests.
Differential Revision: https://phabricator.services.mozilla.com/D21774
--HG--
extra : moz-landing-system : lando
Changes:
- modified the criteria for using 1 as the successful return code by using a combination of factors; is it Windows, is it 32bit, and is it Reftest.
Differential Revision: https://phabricator.services.mozilla.com/D21596
--HG--
extra : moz-landing-system : lando
The bulk of this is copy/pasted from a standard android-api-16 debug
build. The only changes are a few extra environment variables in the
taskcluster config, the subconfig file, and the mozconfig, as well as
the --enable-mozsearch-plugin flag in the mozconfig.
Depends on D20766
Differential Revision: https://phabricator.services.mozilla.com/D20767
--HG--
extra : moz-landing-system : lando
Bug 1120644 will be used to look into why Windows 7 reftests are still returning 1.
Differential Revision: https://phabricator.services.mozilla.com/D20665
--HG--
extra : moz-landing-system : lando
When running Marionette tests in Taskcluster a default window size
per platform has to be set. Further no screen saver, nor notifications
should be active which could interfere with the focus of the
application. Further there is no need to display the taskbar too.
Differential Revision: https://phabricator.services.mozilla.com/D17156
--HG--
extra : moz-landing-system : lando
This removes all .flake8 files except for the one at the root of the repo.
Instead we use the new 'per-file-ignores' config introduced in 3.7. To ignore
specific errors in a subdirectory, add a line like this to the root .flake8:
[per-file-ignores]
path/to/subdir/*: E100, F200, ...
The reasons for this change are:
1. Unblock flake8 blacklist (bug 1367092).
2. Simplify configuration and code.
3. Encourage more consistent styling.
4. Improve performance.
5. Greater editor consistency.
Differential Revision: https://phabricator.services.mozilla.com/D18354
--HG--
extra : moz-landing-system : lando
This bumps flake8 to version 3.7.5.
This also ignores the new lint rules that were added in the new versions.
These rules are de-marked via comment so we know that they should be enabled at
some point (as opposed to the other rules that are (presumably) ignored
intentionally.
Differential Revision: https://phabricator.services.mozilla.com/D18353
--HG--
extra : moz-landing-system : lando
thunderbird_buildbot.py is no longer necessary now that Thunderbird builds
on Taskcluster.
thunderbird_extra.py is moved into comm-*.
Differential Revision: https://phabricator.services.mozilla.com/D16735
--HG--
extra : moz-landing-system : lando
Mars are now generated by separate repackage tasks, so we don't need mar tools
in L10n builds.
Differential Revision: https://phabricator.services.mozilla.com/D17161
--HG--
extra : moz-landing-system : lando
For shutdown crashes in wpt wse need to ignore the crashes for now
until we have a way of allowing specific ones. So just have a global
flag that permits this.
Differential Revision: https://phabricator.services.mozilla.com/D16836
Sometimes it's unclear which of the errors are leading to a
failure. For example wpt sometimes has PROCESS-CRASH lines that don't
contribute to a failure. To make this easier to understand record the
reason for the failure in the log so it appears in the summaries.
Differential Revision: https://phabricator.services.mozilla.com/D16835
Instead of printing one log message per line about the fact the output
was unstructured, just print one per group of unstructured lines.
Differential Revision: https://phabricator.services.mozilla.com/D16834
Information like the pip path, package name, etc is useful for debugging, but
not for bug classification: Let's try to collect all such failures in one
"Could not install python package" bug. The full command line and retry
attempt history is still retrievable from the log, for debugging purposes.
All that is really required for this ticket is to invoke |mach android
archive-geckoview| after |mach package| in the right place.
But it's actively unhelpful to have this magic in mozharness --
especially since the documentation in `locales.rst` is subtly
incorrect (the environment variables and Make variables don't quite
work as written). So this commit adds a Mach command to do the actual
work and replaces most of the mozharness magic with that command.
Since the l10n Make targets check out the l10n HG repositories
locally, this basically Just Works without the mozharness checkout
steps when developing locally.
Differential Revision: https://phabricator.services.mozilla.com/D12455
--HG--
extra : moz-landing-system : lando
As of bug 1513157, minidump_stackwalk is not installed in the test
docker images, so it needs to be downloaded.
Differential Revision: https://phabricator.services.mozilla.com/D14644
--HG--
extra : moz-landing-system : lando
Rap-P treeherder group for Raptor power tests.
Emit separate PERFHERDER_DATA for power in addition to the performance measurements.
Use magic --host HOST_IP value to have framework load host ip from environment
variable HOST_IP.
The keys in the test_paths dict contain the name of the suite e.g. web-platform-tests-testharness, so specify these
keys rather than the generic web-platform-tests key
Differential Revision: https://phabricator.services.mozilla.com/D14284
--HG--
extra : moz-landing-system : lando
From changeset d0828787e64fa55b535c7e783bc97612f5c30cff from
version-control-tools repository.
Differential Revision: https://phabricator.services.mozilla.com/D13767
--HG--
extra : moz-landing-system : lando
Vendored robustcheckout extension from the version-control-tools
repository revision d78e5c52a0228c3dc8ed03fe43bf749c8e68bd20 without
modifications.
This is needed to support Mercurial 4.8.
Differential Revision: https://phabricator.services.mozilla.com/D11398
--HG--
extra : rebase_source : 31fcf83f3da26245fe588a729e7b38202b53ef19
extra : source : b0805a8cf6eb120525408dd486ca2c362afb2db3