These mozconfigs are no longer used since we stopped doing universal
builds in bug 1295375.
MozReview-Commit-ID: Izz9q1dRskH
--HG--
extra : rebase_source : a7b6f84d56812f0946c78aa054f116747e798300
sutagent is no longer built or used; devicemanagerSUT is completely
unused. After this change, devicemanagerADB is the only implementation of
devicemanager, and test harness options like --dm_trans are eliminated.
Currently the StructuredOutputParser validates all unstructured output against a series of error lists (regexes). However,
before this happens, the mochitest harness is converting all unstructured output to structured 'process_output' messages.
This means that Gecko output is not being checked against the error regexes.
This change ensure that in addition to unstructured output, we also validate 'process_output' messages against the error
lists.
MozReview-Commit-ID: DG6sZqpg5aw
--HG--
extra : rebase_source : 8d57c20cfb5690c6b10e0fccad56ad678647e5a8
Currently the StructuredOutputParser validates all unstructured output against a series of error lists (regexes). However,
before this happens, the mochitest harness is converting all unstructured output to structured 'process_output' messages.
This means that Gecko output is not being checked against the error regexes.
This change ensure that in addition to unstructured output, we also validate 'process_output' messages against the error
lists.
MozReview-Commit-ID: DG6sZqpg5aw
--HG--
extra : rebase_source : d07522ff9de09af5506d224885f452dae6ab8144
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
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
BBB schedules macosx64 debug unit tests, but opt is schedule by buildbot
itself.
MozReview-Commit-ID: I8FqzCHgzga
--HG--
extra : rebase_source : fe53957c39ddb625cb47b7ddced1cee83e6f9db3
Currently the StructuredOutputParser validates all unstructured output against a series of error lists (regexes). However,
before this happens, the mochitest harness is converting all unstructured output to structured 'process_output' messages.
This means that Gecko output is not being checked against the error regexes.
This change ensure that in addition to unstructured output, we also validate 'process_output' messages against the error
lists.
MozReview-Commit-ID: DG6sZqpg5aw
--HG--
extra : rebase_source : 969d31410ea2674cd58ef356f24a75d46670ae75
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 : 16ed70edd38a53c3279d8632d7cba3df4d5216c3
Joel Maher
Wes Kocher
Mike Shal
Ting-Yu Chou
Carsten "Tomcat" Book
Geoff Brown
Ben Hearsum
Rail Aliiev
Paul Yang
Richard Barnes
Madeleine Chercover
Mihai Tabara
Xidorn Quan
Iris Hsiao
Andrew Halberstadt
Johan Lorenzo
Sebastian Hengst
Aki Sasaki
Chris Manchester
Kartikaya Gupta
Nick Thomas
Mike Hommey
Bryce Van Dyk
Wander Lairson Costa