inspector/sources/debugger-frameworks/frameworks-dom-xhr-event-breakpoints.html too slow |
|||
Issue descriptionIt's in SlowTests, but still times out in debug occasionally: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector%2Fsources%2Fdebugger-frameworks%2Fframeworks-dom-xhr-event-breakpoints.html When the test does pass, it can take >80 seconds. Maybe this should be split into multiple tests, or it should be written as another type of test to make it faster?
,
Aug 9 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ddfc73f1607f8342b1801797648662071df7898b commit ddfc73f1607f8342b1801797648662071df7898b Author: Philip Jägenstedt <foolip@chromium.org> Date: Tue Aug 09 14:46:07 2016 Allow a very slow inspector test to timeout in debug BUG= 635909 TBR=pfeldman@chromium.org Review URL: https://codereview.chromium.org/2228653003 . Cr-Commit-Position: refs/heads/master@{#410670} [modify] https://crrev.com/ddfc73f1607f8342b1801797648662071df7898b/third_party/WebKit/LayoutTests/TestExpectations
,
Aug 18 2016
This test has also been timing out pretty often on the Site Isolation Win bot, which is a release bot. For example: https://build.chromium.org/p/chromium.fyi/builders/Site%20Isolation%20Win/builds/15755 https://build.chromium.org/p/chromium.fyi/builders/Site%20Isolation%20Win/builds/15753 I'm going to allow this to time out in release mode as well to get that bot green.
,
Aug 18 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/92a2b902b2c4af08c69a4f252d6d94f842e3e98d commit 92a2b902b2c4af08c69a4f252d6d94f842e3e98d Author: alexmos <alexmos@chromium.org> Date: Thu Aug 18 18:05:53 2016 Allow a very slow test to time out. In addition to debug builds, frameworks-dom-xhr-event-breakpoints.html has been timing out on Site Isolation Win, which is a Win7 release bot, so allow it to time out on that platform as well. BUG= 635909 TBR=pfeldman@chromium.org NOTRY=true Review-Url: https://codereview.chromium.org/2260593002 Cr-Commit-Position: refs/heads/master@{#412890} [modify] https://crrev.com/92a2b902b2c4af08c69a4f252d6d94f842e3e98d/third_party/WebKit/LayoutTests/TestExpectations
,
Nov 22 2016
,
May 16 2017
There are still NeedsManualRebaseline lines in TestExpectations associated with this bug. Besides rebaselining (with webkit-patch rebaseline or some other mechanism), what else is left to do for this bug?
,
Jun 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bae18458e66bd367dae9c11aa8a185fe90b8eda8 commit bae18458e66bd367dae9c11aa8a185fe90b8eda8 Author: Alexey Kozyatinskiy <kozyatinskiy@chromium.org> Date: Thu Jun 15 10:41:30 2017 [DevTools] reenable frameworks-dom-xhr-event-breakpoints.html TBR=dgozman@chromium.org Bug: chromium:635909 , chromium:683872 Change-Id: I0e1273ea04fe44d769af668c96b5e0b18eae3cc5 Reviewed-on: https://chromium-review.googlesource.com/536912 Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#479665} [modify] https://crrev.com/bae18458e66bd367dae9c11aa8a185fe90b8eda8/third_party/WebKit/LayoutTests/TestExpectations [modify] https://crrev.com/bae18458e66bd367dae9c11aa8a185fe90b8eda8/third_party/WebKit/LayoutTests/inspector/sources/debugger-frameworks/frameworks-dom-xhr-event-breakpoints-expected.txt [modify] https://crrev.com/bae18458e66bd367dae9c11aa8a185fe90b8eda8/third_party/WebKit/LayoutTests/inspector/sources/debugger-frameworks/frameworks-dom-xhr-event-breakpoints.html
,
Jun 15 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by foolip@chromium.org
, Aug 9 2016