RESOLVED INVALID 91218
[Qt] new tests introduced in r122528 fail 
https://bugs.webkit.org/show_bug.cgi?id=91218
Summary [Qt] new tests introduced in r122528 fail
Balazs Ankes
Reported 2012-07-13 04:22:19 PDT
--- /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_performance_attributes_exist_in_object-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_performance_attributes_exist_in_object-actual.txt @@ -4,4 +4,7 @@ +PASS window.performance is defined +PASS window.performance.timing is defined +PASS window.performance.navigation is defined --------------------------------------------------------------------------------------------------------- --- /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect-actual.txt @@ -5,7 +5,14 @@ -FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1" +FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1"(stack: assert@http://127.0.0.1:8000/w3c/resources/testharness.js:1646 +assert_equals@http://127.0.0.1:8000/w3c/resources/testharness.js:567 +http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +step@http://127.0.0.1:8000/w3c/resources/testharness.js:876 +test@http://127.0.0.1:8000/w3c/resources/testharness.js:338 +wp_test@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:67 +test_equals@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +global code@http://127.0.0.1:8000/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect.html:78) PASS window.performance is defined PASS window.performance.navigation is defined PASS timing.navigation.type is TYPE_NAVIGATE ---------------------------------------------------------------------------------------------------------- --- /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html5/test_performance_attributes_exist_in_object-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html5/test_performance_attributes_exist_in_object-actual.txt @@ -4,4 +4,7 @@ +PASS window.performance is defined +PASS window.performance.timing is defined +PASS window.performance.navigation is defined ---------------------------------------------------------------------------------------------------------- --- /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html5/test_timing_xserver_redirect-expected.txt +++ /ramdisk/qt-linux-64-release/build/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html5/test_timing_xserver_redirect-actual.txt @@ -5,7 +5,14 @@ -FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1" +FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1"(stack: assert@http://127.0.0.1:8000/w3c/resources/testharness.js:1646 +assert_equals@http://127.0.0.1:8000/w3c/resources/testharness.js:567 +http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +step@http://127.0.0.1:8000/w3c/resources/testharness.js:876 +test@http://127.0.0.1:8000/w3c/resources/testharness.js:338 +wp_test@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:67 +test_equals@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +global code@http://127.0.0.1:8000/w3c/webperf/approved/navigation-timing/html5/test_timing_xserver_redirect.html:78) PASS window.performance is defined PASS window.performance.navigation is defined PASS timing.navigation.type is TYPE_NAVIGATE
Attachments
Add attachment proposed patch, testcase, etc.
Ádám Kallai
Comment 1 2012-07-13 07:12:14 PDT
Could you check it, please? Is it a correct result? Thanks.
Szilard Ledan
Comment 2 2012-07-13 08:11:44 PDT
These four failing tests have been put to qt skipped list until further discussion. http://trac.webkit.org/changeset/122579/trunk/LayoutTests/platform/qt/Skipped
Ádám Kallai
Comment 3 2012-09-26 08:34:04 PDT
Investigate these results. It seems that these results are correct. I tried to compare the other platforms and the GTK+'s results were equal to Qt results. I'm going to update it and remove it from the skipped list. Do you have any idea? * http/tests/w3c/webperf/approved/navigation-timing/html/test_performance_attributes_exist_in_object.html --- /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_performance_attributes_exist_in_object-expected.txt +++ /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_performance_attributes_exist_in_object-actual.txt @@ -4,4 +4,7 @@ +PASS window.performance is defined +PASS window.performance.timing is defined +PASS window.performance.navigation is defined * http/tests/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect.html --- /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect-expected.txt +++ /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect-actual.txt @@ -5,7 +5,14 @@ -FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1" +FAIL Starting document.location.hostname is correct (127.0.0.1:8000) assert_equals: Starting document.location.hostname is correct (127.0.0.1:8000) expected "127.0.0.1:8000" but got "127.0.0.1"(stack: assert@http://127.0.0.1:8000/w3c/resources/testharness.js:1646 +assert_equals@http://127.0.0.1:8000/w3c/resources/testharness.js:567 +http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +step@http://127.0.0.1:8000/w3c/resources/testharness.js:876 +test@http://127.0.0.1:8000/w3c/resources/testharness.js:338 +wp_test@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:67 +test_equals@http://127.0.0.1:8000/w3c/webperf/resources/webperftestharness.js:145 +global code@http://127.0.0.1:8000/w3c/webperf/approved/navigation-timing/html/test_timing_xserver_redirect.html:78) PASS window.performance is defined PASS window.performance.navigation is defined PASS timing.navigation.type is TYPE_NAVIGATE
Jocelyn Turcotte
Comment 4 2014-02-03 03:21:41 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.
Note You need to log in before you can comment on or make changes to this bug.