"http/tests/devtools/coverage/multiple-instances-merge.js" is flaky |
||
Issue description"http/tests/devtools/coverage/multiple-instances-merge.js" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyQwsSBUZsYWtlIjhodHRwL3Rlc3RzL2RldnRvb2xzL2NvdmVyYWdlL211bHRpcGxlLWluc3RhbmNlcy1tZXJnZS5qcww. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Jun 1 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6989818705413dc6a4baa974ca7ff14728e858db commit 6989818705413dc6a4baa974ca7ff14728e858db Author: Kim Paulhamus <kpaulhamus@chromium.org> Date: Fri Jun 01 19:46:16 2018 Disable flaky test multiple-instances-merge Tbr: tkent@chromium.org Bug: 848799 Change-Id: I8827afa81214748081cce3a212b76129fbe2d87f Reviewed-on: https://chromium-review.googlesource.com/1082718 Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org> Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org> Cr-Commit-Position: refs/heads/master@{#563760} [modify] https://crrev.com/6989818705413dc6a4baa974ca7ff14728e858db/third_party/WebKit/LayoutTests/TestExpectations
,
Jun 1 2018
,
Jul 6
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fa8b12920e8c2042e47816d004b113c155e81aee commit fa8b12920e8c2042e47816d004b113c155e81aee Author: Alexis Hetu <sugoi@google.com> Date: Fri Jul 06 14:14:32 2018 Attempt to unmark some tests as slow/timeout Now that SwiftShader is on Linux/Windows/MacOS and that a recent performance improvement has been landed in SwiftShader, verify which tests still require the Slow/Timeout markers and which don't. TBR=kbr@chromium.org Bug:chromium:24182 chromium:433711 chromium:763197 chromium:311482 chromium:243871 chromium:664857 chromium:9798 chromium:237270 chromium:241576 chromium:241869 chromium:246749 chromium:535478 chromium:363029 chromium:364225 chromium:552556 chromium:570656 chromium:584807 chromium:614910 chromium:791659 chromium:726075 chromium:808153 chromium:816045 chromium:693568 chromium:626703 chromium:703533 chromium:786641 chromium:799137 chromium:831686 chromium:831230 chromium:818324 chromium:810437 chromium:847205 chromium:848799 chromium:828962 chromium:849284 chromium:855055 Change-Id: I5d36d20bd87b234fefe4da3ea7e4af039c0188cb Reviewed-on: https://chromium-review.googlesource.com/1102341 Reviewed-by: Alexis Hétu <sugoi@chromium.org> Commit-Queue: Alexis Hétu <sugoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#572962} [modify] https://crrev.com/fa8b12920e8c2042e47816d004b113c155e81aee/third_party/WebKit/LayoutTests/SlowTests [modify] https://crrev.com/fa8b12920e8c2042e47816d004b113c155e81aee/third_party/WebKit/LayoutTests/TestExpectations |
||
►
Sign in to add a comment |
||
Comment 1 by kpaulhamus@chromium.org
, Jun 1 2018Status: Assigned (was: Untriaged)