Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(390)

Issue 2827073002: Reland of In run-webkit-tests, start xvfb if necessary. (Closed)

Created:
3 years, 8 months ago by qyearsley
Modified:
3 years, 8 months ago
Reviewers:
Dirk Pranke, kochi, mithro
CC:
blink-reviews, chromium-reviews, ojan
Target Ref:
refs/heads/master
Project:
chromium
Visibility:
Public.

Description

Reland of "In run-webkit-tests, start xvfb if necessary". Original CL (https://codereview.chromium.org/2821543003) broke Android. This is intended to be a reland of the original with modifications; it should only be committed after we get a successful run on android_blink_rel. BUG=711515 Review-Url: https://codereview.chromium.org/2827073002 Cr-Commit-Position: refs/heads/master@{#465778} Committed: https://chromium.googlesource.com/chromium/src/+/b8cba92beb55b43eba8fb7699452f7a278fc2398

Patch Set 1 #

Patch Set 2 : Make a minor change in the order of steps in Manager._set_up_run #

Unified diffs Side-by-side diffs Delta from patch set Stats (+83 lines, -7 lines) Patch
M third_party/WebKit/Tools/Scripts/webkitpy/common/system/executive_mock.py View 1 1 chunk +3 lines, -0 lines 0 comments Download
M third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/controllers/manager.py View 1 2 chunks +8 lines, -7 lines 0 comments Download
M third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/linux.py View 1 3 chunks +42 lines, -0 lines 0 comments Download
M third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/linux_unittest.py View 1 1 chunk +30 lines, -0 lines 0 comments Download

Messages

Total messages: 13 (6 generated)
qyearsley
Created Reland of In run-webkit-tests, start xvfb if necessary.
3 years, 8 months ago (2017-04-19 15:53:37 UTC) #1
qyearsley
It looks like changing the order of the steps executed in manager.py does fix the ...
3 years, 8 months ago (2017-04-19 20:11:30 UTC) #4
Dirk Pranke
lgtm
3 years, 8 months ago (2017-04-19 20:15:28 UTC) #5
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2827073002/130001
3 years, 8 months ago (2017-04-19 20:52:36 UTC) #7
commit-bot: I haz the power
Committed patchset #2 (id:130001) as https://chromium.googlesource.com/chromium/src/+/b8cba92beb55b43eba8fb7699452f7a278fc2398
3 years, 8 months ago (2017-04-19 22:16:22 UTC) #10
kochi
After this commit, showing result summary HTML from run_layout_tests.py complains that [2007:2007:0420/135756.036924:ERROR:browser_main_loop.cc(279)] Gtk: cannot open ...
3 years, 8 months ago (2017-04-20 05:00:50 UTC) #12
qyearsley
3 years, 8 months ago (2017-04-20 16:33:49 UTC) #13
Message was sent while issue was closed.
On 2017/04/20 at 05:00:50, kochi wrote:
> After this commit, showing result summary HTML from
> run_layout_tests.py complains that
> 
> [2007:2007:0420/135756.036924:ERROR:browser_main_loop.cc(279)] Gtk: cannot
open display: :99
> 
> because this script does not revert the change to the
> DISPLAY env var?

Ah, that's right -- more discussion in the bug http://crbug.com/711515

Powered by Google App Engine
This is Rietveld 408576698