diff options
| author | msw <msw@chromium.org> | 2015-07-14 16:36:04 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-07-14 23:36:41 +0000 |
| commit | 11ac9a20850acff9217d4ca7da34353b55d180a8 (patch) | |
| tree | 9b7764c8f5c427071c4d43e552872d33b8b625e3 /components/proximity_auth | |
| parent | 296319ccdb96f3f31df22f3b4ced4e040a864210 (diff) | |
| download | chromium_src-11ac9a20850acff9217d4ca7da34353b55d180a8.zip chromium_src-11ac9a20850acff9217d4ca7da34353b55d180a8.tar.gz chromium_src-11ac9a20850acff9217d4ca7da34353b55d180a8.tar.bz2 | |
Let Python scripts start and stop xvfb manually.
Like build/scripts/slave/xvfb.py, this has some benefits:
It lets Python test runners avoid wrapping commandlines.
It allows separate control of xvfb and test subprocesses.
This also unblocks work on mojo/tools/apptest_runner.py.
(aids killing and getting output of hung test subprocesses)
This also removes the unused get_xvfb_path function.
TODO: Store the xvfb pid in env['_CHROMIUM_INSIDE_XVFB']?
TODO: Use a pid file like build/scripts/slave/xvfb.py?
TODO: Additional refactoring?
BUG=478244
TEST=No xvfb script regressions.
R=dpranke@chromium.org
Review URL: https://codereview.chromium.org/1239563003
Cr-Commit-Position: refs/heads/master@{#338769}
Diffstat (limited to 'components/proximity_auth')
0 files changed, 0 insertions, 0 deletions