Summary: | [Qt] tst_QQuickWebView::basicRenderingSanity() fails on first pixel test. | ||
---|---|---|---|
Product: | WebKit | Reporter: | WebKit Review Bot <webkit.review.bot> |
Component: | New Bugs | Assignee: | Rafael Brandao <rafael.lobo> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | cmarcelo, ossy, rafael.lobo |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | |||
Bug Blocks: | 70236 |
Description
WebKit Review Bot
2012-07-20 14:11:43 PDT
Strangely, if you change QTest::qWait(200) for QTest::wait(400), all comparisons pass. When it fails, it get pixel black instead of green for the first pixel comparison. (In reply to comment #1) > Strangely, if you change QTest::qWait(200) for QTest::wait(400), all comparisons pass. When it fails, it get pixel black instead of green for the first pixel comparison. After switching to a faster machine, I can no longer reproduce this failure. :-( Ossy, any of the guys on Szeged can still reproduce it? I see that our buildbot is failing on it. I think we could investigate how we can switch this qWait for signal wait, or switch the timer value for a higher value if there's no other way? What do you think? Maybe someone that can still reproduce it should fix it. Sure, will check tomorrow. Thanks for the investigation. I checked the bot history, but I didn't find failing tst_QQuickWebView::basicRenderingSanity() test. === 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. |