Currently, tooltool is a python script, but when called from mozharness,
it's wrapped with a shell script. What happens is that mozharness gets
the msys-style paths, passes them to the shell script, then the shell
script calls the python tooltool, and the transition msys->win32 makes
that call use windows style paths.
For bug 1313111, I want to replace tooltool with a mach command, and the
shell script would go away. Calling a mach command (or python tooltool,
for that matter) directly from mozharness with a msys-style path doesn't
work.
OTOH, calling the current shell script with a Windows style path (with
forward slashes, for good measure) does work, and is future-proof.
--HG--
extra : rebase_source : 3cb28d2352fbc2dcac96ae740c5f1aaa0e4a5f0f
This formats the marionette-harness python tests to be a regular |mach python-test| suite. Though
we add subsuite=marionette, this is just for automation purposes. The new preferred way to run the
marionette harness tests locally is:
./mach python-test testing/marionette
They will also run if running the full suite.
The mozbase packages.txt file modifies mozlog to use 'setup.py' instead of 'pth'. The reason for
this is that the marionette-harness tests use the pytest_mozlog pytest plugin for formatting
their results (converts pytest format into something resembling the standard tbpl logging format).
In order for this plugin to get picked up however, mozlog's setup.py file needs to be processed.
MozReview-Commit-ID: Ata99evHxbd
--HG--
extra : rebase_source : 22382e3d65ce8454a1682cfced0d03477762e8fe
This gets raised when trying to run the marionette-harness python tests without an objdir.
It's safe to ignore because mozinfo.json will still be found via the 'dirs' variable which
gets passed in from the marionette harness.
MozReview-Commit-ID: Ata99evHxbd
--HG--
extra : rebase_source : 6e3910667146b9caf0a9abe9a707b34627ba272b
Right now the base run_media_tests function doesn't set the self.return_code
value based on the result of the job result parser. Overrides of the function
appear to need to set this value if it's to be used.
This changeset moves the logic to set this value from the buildbot script to the
base. Overrides are free to alter the behaviour so that the value can be set as
appropriate depending on the tests, but removes the ability to footgun by
assuming that the base will set the value (as I did).
MozReview-Commit-ID: FBT0N62ydR9
--HG--
extra : rebase_source : d6e6f308809d50df92bca4620df0be200bb65f6b
This syncs the implementation of "process an input source action sequence"
with the Webdriver spec.
Previously, Marionette populated the input state table at dispatch time.
MozReview-Commit-ID: 8v1y5uVvrI5
--HG--
extra : rebase_source : b8dabf16baa85aa7b3af1882846055a0e260232e
Proof of concept to be replaced with more tests in a
follow-up.
MozReview-Commit-ID: 8FHJOgpO1wr
--HG--
extra : rebase_source : a4785c01941e6d8a62aca1e91808576894e95e61
Pen and touch support will be added this quarter.
MozReview-Commit-ID: GH7CVNoDOIm
--HG--
extra : rebase_source : 48edfc980a663914636ab3be5e786d5f15cfb41c
Previously, the pointer input state was always being created
with an undefined subtype, which should actually be mouse, pen
or touch.
MozReview-Commit-ID: JcarsRRecQl
--HG--
extra : rebase_source : 4130d3e5cd0dc2d953fdf48e3591de7b0f53383e
Provide more control over event properties to caller.
Changes are based on testing/mochitest/tests/SimpleTest/EventUtils.js
MozReview-Commit-ID: 1p04Fv086Bj
--HG--
extra : rebase_source : 827b91fb2c3e7970e53f5641308b69887eb1041a
Rail Aliiev
Nick Thomas
Mike Hommey
Tomislav Jovanovic
Richard Barnes
Wes Kocher
Mark Banner
Geoff Brown
Ben Kelly
Ryan VanderMeulen
Andrew Halberstadt
Bryce Van Dyk
Ho-Pang Hsu
Carsten "Tomcat" Book
Andrea Marchesini
Sebastian Hengst
Benjamin Bouvier
Joel Maher
Jon Coppeard
Maja Frydrychowicz