Changes:
- for macosx1014, in the tests where `subprocess` is called and the process relies on `six` being present, ensure that `six` is available in the PYTHONPATH by explicitly inserting the contents of `sys.path` to the modified environment variable dict
- change how the command line call to run the suite is being built in `taskcluster/taskgraph/transforms/job/mach.py`
- migrate source-tests from macosx1010 to macosx1014
Differential Revision: https://phabricator.services.mozilla.com/D36681
--HG--
extra : moz-landing-system : lando
This test is working with minimal effort. Let's get it running to prevent
future regressions.
Differential Revision: https://phabricator.services.mozilla.com/D36098
--HG--
extra : moz-landing-system : lando
Android profile runs don't always fully write out the profile data. In
this case, the corrupted profile data is successfully uploaded, but
future profile-use PGO builds try to merge the data and fail. Retrying
the profile-use builds doesn't help, since they all pull from the same
job that published the corrupt data.
We can detect this in the run task by using llvm-profdata merge, and if
the merge fails the task can automatically be retried. Note that the
data gets redundantly merged in the profile-use build, but it may not be
possible to run the merge in the run task on all platforms (eg: OSX), so
we have to keep the merge there as well.
Differential Revision: https://phabricator.services.mozilla.com/D36294
--HG--
extra : moz-landing-system : lando
When adding Windows compatibility in bug 1557785, we stopped exported
UPLOAD_PATH by default. UPLOAD_PATH is used by profileserver.py to
determine where to store the logs; when it is unset, the logs go to
stdout and the artifacts aren't created. We should always export
UPLOAD_PATH to get the same logging behavior on all platforms.
Differential Revision: https://phabricator.services.mozilla.com/D36521
--HG--
extra : moz-landing-system : lando
AWSY is built on marionette, so it inherits the option by default, we mostly
just need to propagate it properly. This also drops the --disable-webrender
option as it is now implied if --enable-webrender is not provided.
Differential Revision: https://phabricator.services.mozilla.com/D35863
--HG--
extra : moz-landing-system : lando
These changes are needed for consistently green runs with the new emulator with
"-gpu on".
Most changes are simple removal of fuzzy-if(geckoview) but I also needed to add
at least one new fuzzy-if.
In this configuration we can run reftests in just 2 chunks (20 minutes each on
opt/30 minutes on debug).
Differential Revision: https://phabricator.services.mozilla.com/D36258
--HG--
extra : moz-landing-system : lando
Updating to the new emulator avoids the network oddities observed in bug 1534732, but
there are a couple of tests that need to be skipped for a consistently green run.
Performance is improved, so we can run in fewer chunks. /opt is reliable, so moving
to tier 1; /debug is reliable except for existing perma-fail bug 1560736.
Differential Revision: https://phabricator.services.mozilla.com/D36260
--HG--
extra : moz-landing-system : lando
Upgrade to version 29.0.11 of the emulator and use '-gpu on' rather than
swiftshader_indirect, for most Android 7.0 tests. The upgrade appears to
finally resolve bug 1534732, improves reftest performance dramatically, and
allows us to reduce reftest "fuzz" for many tests.
marionette tests are excluded because they intermittently fail with network
errors (address in use); these tests are near end-of-life, so I don't think
this issue is worth investigating, but I'll file a follow-up bug to record
the issue.
web-platform tests are excluded because they are not very stable on the
existing emulator, making it difficult to compare results. I will file a
follow-up and work with :maja_zf to see if they can be upgraded soon.
Differential Revision: https://phabricator.services.mozilla.com/D36256
--HG--
extra : moz-landing-system : lando
This patch adds idle browser (*-idle-bg)tests to Raptor which have the app running on about:blank in the background for 20 minutes. It adds the 'background_test' flag to 'scenario' type Raptor tests to make a test run in the background. Furthermore, a unit test is added to the Raptor control server tests as well as methods to check if the app was properly backgrounded or foregrounded.
Differential Revision: https://phabricator.services.mozilla.com/D32428
--HG--
extra : moz-landing-system : lando
Tests are imported from test262 upstream so this test suite is expected to become slower over time.
Differential Revision: https://phabricator.services.mozilla.com/D36295
--HG--
extra : moz-landing-system : lando
Reusing sessions doesn't actually save that much time and avoids a lot of
hard-to-debug intermittents.
Differential Revision: https://phabricator.services.mozilla.com/D32578
--HG--
extra : moz-landing-system : lando
Adds a new release-partner-repack-bouncer-sub-firefox task to add the partner products. This is forked from the main bouncer submission because it diverges sufficiently that this is a cleaner approach. The get_partners_to_be_published helper is used by aliases too.
Depends on D34950
Differential Revision: https://phabricator.services.mozilla.com/D35481
--HG--
extra : moz-landing-system : lando
Appends the customized stub installer and it's gpg signature to the list of artifacts to beetmove to
candidates.
Differential Revision: https://phabricator.services.mozilla.com/D34950
--HG--
extra : moz-landing-system : lando
On win32, where repack_stub_installer is enabled, extend the inputs to the partner repackage task so that it
donwloads the upstream artifacts and creates the stub installer.
Differential Revision: https://phabricator.services.mozilla.com/D34946
--HG--
extra : moz-landing-system : lando
Pay attention to the new repack_stub_installer param, and fix config parsing to split on the first =.
Differential Revision: https://phabricator.services.mozilla.com/D34945
--HG--
extra : moz-landing-system : lando
