This fixes a regression to |mach talos-test| around a missing 'mozterm'
dependency.
MozReview-Commit-ID: GcfoA4U1fqg
--HG--
extra : rebase_source : 68c743165a03c4d9975676556252816793ba9d49
The clean-up code in FennecInstance now counts and logs consecutive DMErrors.
The Marionette clean-up code then throws an UnresponsiveInstanceException
if we hit consecutive errors more than twice, which interrupts the
test run entirely. (Previously, MarionetteTestRunner would just keep running
tests despite consecutive clean-up failures, and eventually it would time out.)
This change allows us to take advantage of the retry mechanism in the
mozharness script that runs all Android tests: it sets the job status to "retry"
if it finds DMError in the test log after the run_tests step is done.
MozReview-Commit-ID: J36XuFVK1aK
--HG--
extra : rebase_source : 99914fd768522fe45160f171966a5efc65c59cc2
The clean-up code in FennecInstance now counts and logs consecutive DMErrors.
The Marionette clean-up code then throws an UnresponsiveInstanceException
if we hit consecutive errors more than twice, which interrupts the
test run entirely. (Previously, MarionetteTestRunner would just keep running
tests despite consecutive clean-up failures, and eventually it would time out.)
This change allows us to take advantage of the retry mechanism in the
mozharness script that runs all Android tests: it sets the job status to "retry"
if it finds DMError in the test log after the run_tests step is done.
MozReview-Commit-ID: J36XuFVK1aK
--HG--
extra : rebase_source : 4feada21d7b4260e73054339fa79c61911d259ee
There are many gotchas to be aware of when working on Marionette
source code. It would be a good idea to collect this in a single
document that could serve as documentation in onboarding new
developers.
DONTBUILD
MozReview-Commit-ID: DuVqckA7wLP
OSX (cross) repackages are currently using a tooltool manifest to get
libdmg and hfsplus. Change those jobs to use the toolchain artifacts
instead.
At the same time, modify the repackage mozharness script's _run_tooltool
so that it doesn't fail with MOZ_TOOLCHAINS being set but without a
tooltool_manifest_src, matching the similar function in buildbase.py.
--HG--
extra : rebase_source : d128d4709c5d1d28d1a6b9c585fde82e99f725c7
It turns out that in all cases it was the last tooltool manifest entry,
so we can remove the tooltool manifests entirely, and remove all
references to them.
--HG--
extra : rebase_source : d8447b5422e63e88444008fddb76d658829694de
We're about to remove some tooltool manifests, so we need those calls to
work properly when TOOLTOOL_MANIFEST is not set.
--HG--
extra : rebase_source : 89d41021a87915dc9133e61543352e3bda1dace4
According to :birtles, it is not guaranteed that animationiteration
event will be fired. This event is sample-based rather than event-based,
and such behavior has been clarified in CSS Animations Level 2:
https://drafts.csswg.org/css-animations-2/#event-dispatch
Also, Chromium has the same issue with this test:
https://bugs.chromium.org/p/chromium/issues/detail?id=701445
MozReview-Commit-ID: KBCzkGHxbfc
--HG--
extra : rebase_source : 0b187471ee7625316ad8c85dc1698cb7099dc887
This removes the subcommands for "./mach geckodriver", reverting
it back to have the meaning of running the geckodriver binary.
The build- and test commands are now integrated with mach, which
means you can run "./mach build testing/geckodriver" and "./mach
test testing/geckodriver" to run tests. This is backed by a new
top-level "./mach geckodriver-test" command, which we will not be
announcing.
MozReview-Commit-ID: CiQsfNqrvIp
--HG--
extra : rebase_source : 6c492b7e1128e4858e42ae4bb35ab4b29564dbeb
Rob Wood
Andreea Pavel
Geoff Brown
Andrew Halberstadt
Maja Frydrychowicz
Vedant Chakravadhanula
Alexandre Poirot
Noemi Erli
Ryan VanderMeulen
Cosmin Sabou
Ciure Andrei
James Graham
Olli Pettay
Sebastian Hengst
Marco Castelluccio
Jon Coppeard
arthur.iakab
Gurzau Raul
Andreas Tolfsen
Robert Longson
Mike Hommey
Gijs Kruitbosch
Xidorn Quan