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
Make sure ProcessHandlerMixin.Process works also under 3.6.
3.6 introduced a _wait() method in its Popen class, that
conflicts with the one in mozprocess. The patch renames it
and also adds timeout where possible.
Differential Revision: https://phabricator.services.mozilla.com/D22157
--HG--
extra : moz-landing-system : lando
Cue might have negative length because user can set cue's end time via `TextTrackCue`'s API and the spec doesn't have strong restriction that the end time should be equal or larger than the start time of the cue.
As the negative length cue won't be displayed, we have no need to add it to the `other cues`.
[1] https://html.spec.whatwg.org/multipage/media.html#dom-texttrackcue-endtime
Differential Revision: https://phabricator.services.mozilla.com/D24857
--HG--
extra : moz-landing-system : lando
`Selection::Extend()` is too slow because:
- it may create some `nsRange` instances.
- it users `nsContentUtils::ComparePoints()` multiple times.
Therefore, we can improve the performance if we can stop using it in some
places. First, this patch creates `Selection::SetStartAndEnd()` and
`Selection::SetStartAndEndInLimiter()` for internal use. They remove
current ranges, reuse `nsRange` instance as far as possible and add new
range which is set by their arguments. Then, this patch makes
`Selection::SelectAllChildren()` stop using `Selection::Extend()`. At this
time, this fixes a web-compat issue. `Selection::Expand()` cannot cross the
selection limiter boundary when there is a limiter (e.g., when an editing host
has focus). But we can now fix this with using the new internal API.
Note that methods in editor shouldn't move selection to outside of active
editing host. Therefore, this patch adds `Selection::SetStartAndEndInLimiter()`
and `Selection::SetBaseAndExtentInLimiter()` for them.
Differential Revision: https://phabricator.services.mozilla.com/D23459
--HG--
extra : moz-landing-system : lando
In normal cases, `PresShell::EventHandler` won't receive untrusted event.
However, only `nsIDOMWindowUtils.dispatchDOMEventViaPresShell()` may send
untrusted event if its `aTrusted` is false. Currently, this is not used by
chrome so that we don't need to keep supporting it for dispatching untrusted
events.
This patch removes `aTrusted` argument from it.
Differential Revision: https://phabricator.services.mozilla.com/D24870
--HG--
extra : moz-landing-system : lando
The `tabModal` property getter can return null so we need to check it before accessing sub-properties.
Differential Revision: https://phabricator.services.mozilla.com/D24738
--HG--
extra : moz-landing-system : lando
selection.py is used only by AccessibleCaret tests.
Differential Revision: https://phabricator.services.mozilla.com/D24447
--HG--
rename : testing/marionette/client/marionette_driver/selection.py => layout/base/tests/marionette/selection.py
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
Currently, tests in mozsystemmonitor are skipped because the manifest is missing
from mozbase/moz.build. This has now been added.
For the moment, this patch also skips the test if run against Python 3. This is
not ideal - a better fix may be setting the unittest.skipIf condition to skip
if the there is simply a failure when run with Python 3.
Differential Revision: https://phabricator.services.mozilla.com/D22426
--HG--
extra : moz-landing-system : lando
Unifies the mochitest MOZ_LOG file naming and archiving across desktop/android.
Notably the inclusion of pid and uuid for android log files helps generate
appropriate files for e10s on geckoview.
Differential Revision: https://phabricator.services.mozilla.com/D24262
--HG--
extra : moz-landing-system : lando
This parses the metadata files without evaluating the conditional
expressions, producing a JSON summary file in which each possible
condition is represented as a string.
Not all data from the metadata files appears in the summary, only
exceptional cases likely to be of interest to engineers and unlikely
to be on wpt.fyi e.g. tests that have lsan leaks or tests that crash,
not just tests that fail. This is intended to keep the filesize down.
Depends on D24177
Differential Revision: https://phabricator.services.mozilla.com/D24178
--HG--
extra : moz-landing-system : lando
The manifest compilers follow a mostly common design so it seems
reasonable to put the common parts into a base class, and allow
subclasses to override the functionaility where required.
Differential Revision: https://phabricator.services.mozilla.com/D24177
--HG--
rename : testing/web-platform/tests/tools/wptrunner/wptrunner/wptmanifest/backends/static.py => testing/web-platform/tests/tools/wptrunner/wptrunner/wptmanifest/backends/base.py
extra : moz-landing-system : lando
Ciure Andrei
Andrew Halberstadt
Emilio Cobos Álvarez
Julian Descottes
Sebastian Streich
Tarek Ziadé
Rob Wood
Mats Palmgren
Alastor Wu
Coroiu Cristina
Byron Campen [:bwc]
Csoregi Natalia
Masayuki Nakano
James Graham
Bogdan Tara
Matt Woodrow
Eric Rahm
shindli
Ting-Yu Lin
Henrik Skupin
Edwin Gao
Cosmin Sabou
Tom Prince
arthur.iakab
Nikki S
Geoff Brown
Sebastian Hengst
Olli Pettay
Andreea Pavel
Daniel Varga