98343 2012-10-03 23:52:09 -0700 [Qt][WK2] fast/dom/Geolocation/window-close-crash.html times out 2014-02-03 03:22:51 -0800 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) All All RESOLVED INVALID Qt, QtTriaged P2 Normal --- 79668 97608 1 ossy webkit-unassigned benjamin ossy sam oldest_to_newest 734407 0 ossy 2012-10-03 23:52:09 -0700 fast/dom/Geolocation/window-close-crash.html was unskipped from wk2 by https://trac.webkit.org/changeset/130325, but it fails with notifydone timeout on Qt WK2: --- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/fast/dom/Geolocation/window-close-crash-expected.txt +++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/fast/dom/Geolocation/window-close-crash-actual.txt @@ -1,14 +1,2 @@ -Tests the assertion that the GeolocationClient should not be updating -when the GeolocationController is destroyed. -See https://bugs.webkit.org/show_bug.cgi?id=52216 +FAIL: Timed out waiting for notifyDone to be called -On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". - - -Main page opening resources/window-close-popup.html -PASS Received Geoposition. -PASS Success - no crash! -PASS successfullyParsed is true - -TEST COMPLETE - 734418 1 ossy 2012-10-04 00:12:16 -0700 I skipped it to paint the bot green - r130367 Please unskip it with the proper fix. 734874 2 benjamin 2012-10-04 11:33:25 -0700 https://bugs.webkit.org/show_bug.cgi?id=98212 may fix that for you. If not check your platform. 737445 3 ossy 2012-10-08 23:19:58 -0700 Nothing changed, the test still fails with notifydone timeout. 737467 4 benjamin 2012-10-08 23:50:26 -0700 (In reply to comment #3) > Nothing changed, the test still fails with notifydone timeout. It is strange, the geolocation tests are now almost completely port independent for WebKit2. If you find out the reason of the timeout, I am interested to hear. 772679 5 ossy 2012-11-21 02:23:52 -0800 still valid bug 772680 6 ossy 2012-11-21 02:24:30 -0800 (In reply to comment #4) > If you find out the reason of the timeout, I am interested to hear. I won't find the reason, because I don't work on it, I only reported this bug. 975565 7 jturcotte 2014-02-03 03:22:51 -0800 === 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.