This patch also removes custom_script and stops
executing start() in the constructor.
Differential Revision: https://phabricator.services.mozilla.com/D23288
--HG--
extra : moz-landing-system : lando
The ability to capture the parent process' stdio is suggested to be a useful feature
to move from web-platform/tests into mozlog. To do so, I have created a new capture.py
file within mozlog/mozlog. This includes the CaptureIO class and its dependencies,
including the LoggingWrapper and LogThread classes. These have been removed from their
original location, to avoid duplication, and the files depending on them updated
accordingly.
It would be useful to add unittests testing the CaptureIO enter and exit methods, and
the original_stdio, logging_queue and logging_thread properties. I have begun such a
file with test_capture.py in mozlog/tests. This is a work in progress, however I may
need some guidance, please, in regards to creating appropriate mock data to assert.
Differential Revision: https://phabricator.services.mozilla.com/D22166
--HG--
extra : moz-landing-system : lando
Adds archive extraction support to download_file_from_url (and also make it py3
compatible)
Differential Revision: https://phabricator.services.mozilla.com/D22662
--HG--
extra : moz-landing-system : lando
Make sure we shutdown the mitmproxy process in case the setup fails.
Differential Revision: https://phabricator.services.mozilla.com/D22467
--HG--
rename : testing/mozbase/mozproxy/tests/test.py => testing/mozbase/mozproxy/tests/test_proxy.py
extra : moz-landing-system : lando
This patch moves testing/raptor/raptor/playback into its own testing package in testing/mozbase/mozproxy
so we can use the proxy in other places than Raptor.
Differential Revision: https://phabricator.services.mozilla.com/D21200
--HG--
rename : testing/raptor/raptor/playback/__init__.py => testing/mozbase/mozproxy/mozproxy/__init__.py
rename : testing/raptor/raptor/playback/base.py => testing/mozbase/mozproxy/mozproxy/backends/base.py
rename : testing/raptor/raptor/playback/mitmproxy.py => testing/mozbase/mozproxy/mozproxy/backends/mitm.py
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-linux64.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-linux64.manifest
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-osx.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-osx.manifest
rename : testing/raptor/raptor/playback/mitmproxy-rel-bin-win.manifest => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy-rel-bin-win.manifest
rename : testing/raptor/raptor/playback/mitmproxy_requirements.txt => testing/mozbase/mozproxy/mozproxy/backends/mitmproxy_requirements.txt
extra : moz-landing-system : lando
The HTML formatter now references the correct link and does not produce a 404 error
Differential Revision: https://phabricator.services.mozilla.com/D21207
--HG--
extra : moz-landing-system : lando
The HTML formatter now references the correct link and does not produce a 404 error
Differential Revision: https://phabricator.services.mozilla.com/D21207
--HG--
extra : moz-landing-system : lando
On the Android 7.0 x86_64 emulator, pidof occasionally returns
no results for a running process. To guard against this case, mozdevice
retries exactly once.
Differential Revision: https://phabricator.services.mozilla.com/D20898
--HG--
extra : moz-landing-system : lando
Improve support for Python 3 by running modernize over adb.py and a few other related changes.
Differential Revision: https://phabricator.services.mozilla.com/D19306
--HG--
extra : moz-landing-system : lando
This bit of code annoyingly runs before we know whether we really need an
emulator or not, so the error blocks testing even with a real device.
Differential Revision: https://phabricator.services.mozilla.com/D19700
--HG--
extra : moz-landing-system : lando
Test manifests may be included by multiple other manifests, optionally
with additional variables below the `[include:...]` section header.
These additional variables are specific to the manifest that contained
the "include" section, and should not inadvertently be shared with other
manifests that also happen to include this manifest.
To achieve that, store the defaults for included manifests in a (path to
parent manifest, path to included manifest) tuple instead of just the
included manifest.
Differential Revision: https://phabricator.services.mozilla.com/D18086
--HG--
extra : moz-landing-system : lando
Windows documentation indicates that it's invalid to WaitForSingleObject
on a process handle unless you request the SYNCHRONIZE access right.
And indeed, we see errors in the logs like:
09:58:28 WARNING - mozcrash kill_pid(): wait failed (-1) terminating pid 6340: error 5
That "error 5" is an ERROR_ACCESS_DENIED code. Such errors should go
away with requesting the proper access rights. Credit to dmajor for
noticing the discrepancy.
Nupur Baghel
Kriti Singh
Tarek Ziadé
Florin Strugariu
Kartikaya Gupta
Nikki S
Andrew Erickson
Florian Quèze
Asfiya
Narcis Beleuzu
Geoff Brown
Coroiu Cristina
Dave Hunt
AndreiH
Andreea Pavel
Jan Henning
James Graham
A. Wilcox
Rob Wu
Razvan Maries
Paolo Amadini
Nathan Froyd
Csoregi Natalia
Pavel Slepushkin
Ciure Andrei
Bob Clary
Myk Melez