Bug 38654

Summary: [Qt][WK1][meta] Fix failing API tests
Product: WebKit Reporter: Jesus Sanchez-Palencia <jesus>
Component: WebKit QtAssignee: Nobody <webkit-unassigned>
Status: RESOLVED INVALID    
Severity: Normal CC: abecsi, ademar, benjamin, cmarcelo, diegohcg, feherzs, hausmann, kenneth, laszlo.gombos, luiz, ossy, tonikitoo, zoltan
Priority: P2 Keywords: Qt, QtTriaged
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Bug Depends on: 37316, 37319, 37322, 37323, 38538, 38655, 38658, 38674, 38675, 38677, 38679, 38681, 38685, 38733, 41064, 41065, 41066, 56946, 57254, 57485, 58031, 58032, 58044, 58847, 59345, 59481, 60372, 60893, 60984, 61042, 61043, 61044, 61045, 61046, 61739, 63235, 63236, 63237, 63244, 63245, 64989, 65170, 65243, 65244, 65452, 65531, 67059, 68711, 72361, 72362, 101571, 102223, 102231, 102233, 102234, 102235, 105820, 107827, 108626, 115855, 116092, 118597, 118659, 118660, 118661, 118663, 118670, 118673, 121825    
Bug Blocks: 55056    

Description Jesus Sanchez-Palencia 2010-05-06 10:08:15 PDT
This is a meta-bug for tracking the work being done on Qt WebKit auto-tests that are failing.
We have multiple failures on Linux, Mac OS and Maemo.
Comment 1 Kenneth Rohde Christiansen 2010-08-29 02:07:30 PDT
cc'ing Benjamin, as he seems to be looking into the autotests.
Comment 2 Ademar Reis 2011-06-20 10:56:00 PDT
We reviewed most of these bugs and some of them are still being activelly worked on, but they won't block the qtwebkit-2.2 release anymore (nevertheless, the bots will be green, with properly expected fails).
Comment 3 Csaba Osztrogonác 2011-10-17 07:11:22 PDT
There is 15 opened bug report to fix API tests for WebKit1 and additionally there are 15 failing API test on the official QtWebKit buildbot on http://build.webkit.org

Is there anybody interested in fixing these bugs?
Comment 4 Jocelyn Turcotte 2014-02-03 03:16:28 PST
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.