diff options
| author | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-15 13:55:08 +0000 |
|---|---|---|
| committer | pliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-15 13:55:08 +0000 |
| commit | 101e2a6e4139710896c564232f77b68250c2d3ec (patch) | |
| tree | 574aeae3b0a184ce1d68c54c573fb59901efa751 /extensions | |
| parent | 4aa880e76a9498497ab3000def7fa0b027fad9c2 (diff) | |
| download | chromium_src-101e2a6e4139710896c564232f77b68250c2d3ec.zip chromium_src-101e2a6e4139710896c564232f77b68250c2d3ec.tar.gz chromium_src-101e2a6e4139710896c564232f77b68250c2d3ec.tar.bz2 | |
Add device port unmapping support to forwarder2.
There used not to be any way to unmap a previously forwarded port. Since
the host and device forwarder processes are kept alive during a whole test
suite, both the host and device ended up with an unnecessarily high amount of
unused open sockets. That is source of flakiness (e.g. too many opened file
descriptors).
This adds an UnmapDevicePort() method to the Python Forwarder wrapper class and
modifies the native forwarder2 to accept a negative port on the command line.
When a negative port is provided, the host forwarder tries to unmap that port
(that was mapped previously).
BUG=229685,239014
R=bulach@chromium.org, digit@chromium.org
Review URL: https://codereview.chromium.org/15008004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200257 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'extensions')
0 files changed, 0 insertions, 0 deletions