Looking at http://build.webkit.org/results/Qt%20Linux%20Release/r116666%20%2846863%29/results.html, it's really not obvious to me why it is failing only on Qt. I inspected the difference but couldn't spot it... AFAICT the other platforms are passing the test so I am going to skip it on Qt for now.
It runs as expected here, maybe it has been fixed?
(In reply to comment #1) > It runs as expected here, maybe it has been fixed? It seems yes, so I unskipped it - https://trac.webkit.org/changeset/116932
Reopen, because it is still valid bug, but for only 32 bit. (I reverted the unskip patch.)
It seems it is related to https://bugs.webkit.org/show_bug.cgi?id=85596 / https://bugs.webkit.org/show_bug.cgi?id=86026
I do have a Qt5 Linux 32 bits environment here, and the test passes regularly (as up to r120320). Might be a good idea to check again on build bot. (In reply to comment #3) > Reopen, because it is still valid bug, but for only 32 bit. > (I reverted the unskip patch.)
It still fails on the bot env. (Qt 4.8 / Qt 5.0 in 32 bit )
Sounds interesting, can you please generate the diff (or is there an easy way to generate it)? (In reply to comment #6) > It still fails on the bot env. (Qt 4.8 / Qt 5.0 in 32 bit )
=== 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.