Allow configuring websocket connection timeout in autotests |
||||
Issue descriptionWe want a way to configure websocket connection timeout in autotests. Currently we have a bug in Chrome that it takes 10+ seconds to establish a websocket connection for devtools in autotests ( Issue 704024 ). While working on proper fixes for the issue, we want a workaround for autotests breakages.
,
Mar 29 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3c7170a0bed4bf8cc9b0a95f5066100bec0f15bb commit 3c7170a0bed4bf8cc9b0a95f5066100bec0f15bb Author: catapult-deps-roller <catapult-deps-roller@chromium.org> Date: Wed Mar 29 12:01:36 2017 Roll src/third_party/catapult/ fdb402a31..83f447ccc (1 commit) https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/fdb402a3169a..83f447ccc94d $ git log fdb402a31..83f447ccc --date=short --no-merges --format='%ad %ae %s' 2017-03-29 nya Increase the websocket timeout in Chrome OS. Created with: roll-dep src/third_party/catapult BUG= 705399 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, see: http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=catapult-sheriff@chromium.org Review-Url: https://codereview.chromium.org/2779053003 Cr-Commit-Position: refs/heads/master@{#460357} [modify] https://crrev.com/3c7170a0bed4bf8cc9b0a95f5066100bec0f15bb/DEPS
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by nya@chromium.org
, Mar 29 2017