Bug 86909

Summary: Many tests (compositing, inspector, etc.) slow/timing out on Chromium Win
Product: WebKit Reporter: Peter Kasting <pkasting>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abarth, enne, jamesr, kbr, nduca, pfeldman, shinyak
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Description Peter Kasting 2012-05-18 15:36:43 PDT
Affected tests include:

compositing/geometry/object-clip-rects-assertion.html
http/tests/inspector/appcache/appcache-iframe-manifests.html
http/tests/inspector/network/async-xhr-json-mime-type.html
http/tests/inspector/network/network-cachedresources-with-same-urls.html
http/tests/inspector/network/network-content-replacement-xhr.html
http/tests/security/escape-form-data-field-names.html
http/tests/security/feed-urls-from-remote.html
http/tests/security/referrer-policy-redirect-link.html
platform/chromium/virtual/gpu/fast/canvas/imagedata-contains-uint8clampedarray.html
platform/chromium/virtual/gpu/fast/canvas/webgl/webgl-composite-modes-repaint.html

There may be several different bugs here (e.g. inspector, GPU, etc.).

CCing some people who are familiar with some of these areas.
Comment 1 James Robinson 2012-05-21 11:27:00 PDT
Any ideas about when this started?

Is it just one bot, or many?
Comment 2 Peter Kasting 2012-05-21 11:29:18 PDT
I got the test list from the union of all the Chromium Windows canary bots.  Most of these looked like they'd been problematic for some time.  You can take a look on the flakiness dashboard for ToT Chromium to see what I saw.
Comment 3 Shinya Kawanaka 2012-10-15 19:17:19 PDT
object-clip-rects-assertion.html sometimes crashes on Windows.

Here is the flakiness dashboard.
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=compositing%2Fgeometry%2Fobject-clip-rects-assertion.html
Comment 4 Stephen Chenney 2013-04-09 17:06:14 PDT
Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.