|
|
Descriptionwebkitpy: Check xvfb with xdpyinfo after starting.
This makes sure that xvfb actually started correctly and you can connect
to it. We don't use -display argument as we want to make sure the
environment is correct.
BUG=713597
Review-Url: https://codereview.chromium.org/2837773002
Cr-Commit-Position: refs/heads/master@{#467253}
Committed: https://chromium.googlesource.com/chromium/src/+/dcdb807ced40e620460ccf56362945e6860db1ab
Patch Set 1 #Patch Set 2 : Use a timeout instead #Patch Set 3 : Use host for time functions #Patch Set 4 : Fixing tests #
Messages
Total messages: 30 (24 generated)
tansell@chromium.org changed reviewers: + mcgreevy@chromium.org, qyearsley@chromium.org
Description was changed from ========== webkitpy: Check xvfb with xdpyinfo after starting. This makes sure that xvfb actually started correctly and you can connect to it. We don't use -display argument as we want to make sure the environment is correct. BUG=713597 ========== to ========== webkitpy: Check xvfb with xdpyinfo after starting. This makes sure that xvfb actually started correctly and you can connect to it. We don't use -display argument as we want to make sure the environment is correct. BUG=713597 ==========
tansell@chromium.org changed reviewers: + dpranke@google.com
The CQ bit was checked by tansell@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by tansell@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
dpranke@chromium.org changed reviewers: + dpranke@chromium.org
lgtm https://codereview.chromium.org/2837773002/diff/20001/third_party/WebKit/Tool... File third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/linux.py (right): https://codereview.chromium.org/2837773002/diff/20001/third_party/WebKit/Tool... third_party/WebKit/Tools/Scripts/webkitpy/layout_tests/port/linux.py:51: XVFB_START_TIMEOUT = 30.0 # Wait up to 30 seconds for Xvfb to start. This seems way too long to wait in general, given that it should be subsecond, but I'm fine w/ it for now for debugging purposes.
tansell@chromium.org changed reviewers: - dpranke@chromium.org
Hi Dirk, PTAL. Tim 'mithro' Ansell
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by tansell@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Patchset #2 (id:20001) has been deleted
The CQ bit was checked by tansell@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by tansell@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by tansell@chromium.org
The CQ bit was checked by tansell@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from dpranke@chromium.org Link to the patchset: https://codereview.chromium.org/2837773002/#ps80001 (title: "Fixing tests")
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 80001, "attempt_start_ts": 1493183180242120, "parent_rev": "bd0fcfc50787bed5d42f1c8fab247234c1a6a20e", "commit_rev": "dcdb807ced40e620460ccf56362945e6860db1ab"}
Message was sent while issue was closed.
Description was changed from ========== webkitpy: Check xvfb with xdpyinfo after starting. This makes sure that xvfb actually started correctly and you can connect to it. We don't use -display argument as we want to make sure the environment is correct. BUG=713597 ========== to ========== webkitpy: Check xvfb with xdpyinfo after starting. This makes sure that xvfb actually started correctly and you can connect to it. We don't use -display argument as we want to make sure the environment is correct. BUG=713597 Review-Url: https://codereview.chromium.org/2837773002 Cr-Commit-Position: refs/heads/master@{#467253} Committed: https://chromium.googlesource.com/chromium/src/+/dcdb807ced40e620460ccf563629... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:80001) as https://chromium.googlesource.com/chromium/src/+/dcdb807ced40e620460ccf563629...
Message was sent while issue was closed.
qyearsley@chromium.org changed reviewers: + dpranke@chromium.org - dpranke@google.com
Message was sent while issue was closed.
LGTM, thanks. I would have had a couple minor nits (nested ifs could be changed to `and`, typo in test method name), but these are not important. |