There was special case logic to map the win64 platform to win32, for stub
entries. When win64-aarch64 was added no special case was added for that
plaform, so they stub entries pointed at the incorrect place. This changes the
configuration so that all stub entries point at the win32 paths, without
needing special case code.
Differential Revision: https://phabricator.services.mozilla.com/D25841
--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
We check that partials as a safety check. But we don't need that for staging builds,
and it is often useful to be able to test things that don't depend on partials.
The shipit UI currently still requires partials, but that can be worked around using
the react dev tools.
Differential Revision: https://phabricator.services.mozilla.com/D24834
--HG--
extra : moz-landing-system : lando
The original code was converting to json, then comparing against `{}`. This switches things
around so that json is only generated where it is directly used a json.
Differential Revision: https://phabricator.services.mozilla.com/D24833
--HG--
extra : moz-landing-system : lando
Enables the list of suites as defined in Bug 1540213.
- added new item in `test-sets.yml` for windows10-aarch64.
- reference the new test-set in `test-platforms.yml`.
Differential Revision: https://phabricator.services.mozilla.com/D25979
--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
Changes:
- skipped problematic tests in crashtest suite on windows10-aarch64
- removed unnecessary pixel fuzzy values from previous iterations of greening tests
Differential Revision: https://phabricator.services.mozilla.com/D25714
--HG--
extra : moz-landing-system : lando
Ran across this while adding `--feature-args`. jstests.py and jit_test.py both
accept `--args`, but with slightly different behavior. The two test runners
should behave the same, as much as reasonably possible. In this case
jit_test.py is doing it right; parsing a string of command-line arguments by
splitting on spaces is not the best idea.
(Alas, this does not fix the ludicrous restriction that `skip-if` expressions
can't have spaces in them.)
Differential Revision: https://phabricator.services.mozilla.com/D25858
--HG--
extra : moz-landing-system : lando
Regular `--args` are ignored when running a `skip-if` or `slow-if` test; these are not.
Differential Revision: https://phabricator.services.mozilla.com/D25856
--HG--
extra : moz-landing-system : lando
Currently TabParent is refcounted, but nsFrameLoader hold a weak pointer. The pointer
should be cleared out when the TabParent is destroyed, but that's a bit of a footgun
and it's not obvious that we always do this correctly.
Because TabParent holds a reference to a nsFrameLoader and the frame element (which
contains a nsFrameLoader), I think this means we need to cycle collect TabParent.
--HG--
extra : rebase_source : 06e04c2ba8ea81d996d2688a1b0064aa37f45bbc
PPluginInstance's __delete__ was ported from rpc to intr, and is the
only non-async IPDL deletion in the codebase. We should be able to
align this with the rest of the IPDL interfaces and remove the need
for specialized intr __delete__ handling.
Differential Revision: https://phabricator.services.mozilla.com/D25674
--HG--
extra : moz-landing-system : lando
Re-enable some tests, and adjust expected outcomes based on the newer multiplier for web platform tests.
This isn't a comprehensive list but covers a good chunk of the disabled tests.
Differential Revision: https://phabricator.services.mozilla.com/D25814
--HG--
extra : moz-landing-system : lando
Some sites use `email`, `tel` and `tel-national` values for @autocomplete even when they are used as the username and 'username' would be more appropriate.
We already allowed type=email / type=tel so allowing the autocomplete equivalents is reasonable.
Differential Revision: https://phabricator.services.mozilla.com/D25883
--HG--
extra : moz-landing-system : lando
Additional test needs to be disabled for widows10-aarch64 due to lack of plugin support.
Differential Revision: https://phabricator.services.mozilla.com/D25889
--HG--
extra : moz-landing-system : lando
