[Qt] storage/statement-error-callback.html failed on Qt Linux Release Bot

• Component: Tools / Tests
• Status: RESOLVED INVALID

[Eric Seidel (no email)]

storage/statement-error-callback.html failed on Qt Linux Release Bot

http://build.webkit.org/results/Qt%20Linux%20Release/r56801%20(9327)/storage/transaction-callback-exception-crash-diffs.txt
--- /home/webkitbuildbot/release32bit/buildslave/qt-linux-release/build/layout-test-results/storage/transaction-callback-exception-crash-expected.txt	2010-03-30 12:26:09.576142618 -0700
+++ /home/webkitbuildbot/release32bit/buildslave/qt-linux-release/build/layout-test-results/storage/transaction-callback-exception-crash-actual.txt	2010-03-30 12:26:09.576142618 -0700
@@ -1,2 +1,3 @@
-CONSOLE MESSAGE: line 0: TransactionCallbackError
+CONSOLE MESSAGE: line 9: INVALID_STATE_ERR: DOM Exception 11: An attempt was made to use an object that is not, or is no longer, usable.
+FAIL: Timed out waiting for notifyDone to be called
 If WebKit doesn't crash, this test has passed

Possibly related to crashes we've seen from this test on the Gtk bot:
https://bugs.webkit.org/show_bug.cgi?id=33294

http://trac.webkit.org/browser/trunk/LayoutTests/storage/statement-error-callback.html

[Dumitru Daniliuc]

The test is transaction-callback-exception-crash.html, not statement-error-callback.html. The INVALID_STATE_ERR happens when trying to open the database. openDatabase() throws this exception in 5 cases:

1. the file could not be opened (disk is full, can't create a new file?).
2. a special table could not be created.
3. the DB version could not be read,
4. the DB version could not be updated.
5. the DB version does not match the version provided in openDatabase().

If this test keeps failing, I'd suggest doing a clean up on the bot. I can't think of any good reason why this test would fail.

[Jocelyn Turcotte]

=== 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.