| Summary: | compositing/transitions/transform-on-large-layer.html is flaky | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Allan Sandfeld Jensen <allan.jensen> | ||||
| Component: | Tools / Tests | Assignee: | Allan Sandfeld Jensen <allan.jensen> | ||||
| Status: | REOPENED --- | ||||||
| Severity: | Normal | CC: | commit-queue, rniwa, simon.fraser, zarvai | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Bug Depends on: | 110027 | ||||||
| Bug Blocks: | 109179 | ||||||
| Attachments: |
|
||||||
|
Description
Allan Sandfeld Jensen
2013-02-18 02:25:14 PST
Created attachment 188833 [details]
Patch
Comment on attachment 188833 [details] Patch Clearing flags on attachment: 188833 Committed r150048: <http://trac.webkit.org/changeset/150048> All reviewed patches have been landed. Closing bug. On Qt Release bot it is still flaky. Ones it timeouts: http://build.webkit.org/results/Qt%20Linux%20Release/r150049%20%2860095%29/results.html http://build.webkit.org/results/Qt%20Linux%20Release/r150050%20%2860096%29/results.html Other case that it has stderr output "FAIL: Timed out waiting for notifyDone to be called" http://build.webkit.org/results/Qt%20Linux%20Release/r150052%20%2860097%29/results.html (In reply to comment #4) > On Qt Release bot it is still flaky. > > Ones it timeouts: > http://build.webkit.org/results/Qt%20Linux%20Release/r150049%20%2860095%29/results.html > http://build.webkit.org/results/Qt%20Linux%20Release/r150050%20%2860096%29/results.html > > Other case that it has stderr output > "FAIL: Timed out waiting for notifyDone to be called" > http://build.webkit.org/results/Qt%20Linux%20Release/r150052%20%2860097%29/results.html Skipped on Qt in http://trac.webkit.org/changeset/150576. Please unskip it with proper fix. This test is still flakey on Mac. And a test with a 1.5s timeout is crazy! I have no idea what this test is trying to do. It seemed to be specific to the chromium compositor, so we should just kill it. (In reply to comment #6) > This test is still flakey on Mac. > > And a test with a 1.5s timeout is crazy! I have no idea what this test is trying to do. It seemed to be specific to the chromium compositor, so we should just kill it. It is not specific to the chromium compositor. It was made for the coordinated graphics (EFL, GTK+ and Qt). We were actually surprised to see this case also fail on Mac and Chromium. Bug 110027 tracks Mac issues with this test, which are not necessarily the same as on other platforms. |