database-lock-after-reload.html has a few problems: 1. Uses the same 'errorFunction' as a statement error callback and transaction error callback. This is not OK, because the two error callbacks have different signatures. 2. Uses RANDOMBLOB which is disallowed by the authorizer. The fact that the test still passes sometimes shows how irrelevant/flaky some operations are. 3. It tries to insert a big enough BLOB in the database, to keep the database thread busy while the main thread navigates to a different page. A 0.5MB BLOB can hardly be considered big enough for this. 4. Some trailing whitespaces.
Created attachment 49873 [details] patch The flakiness of this test should be completely removed by the fix to bug 35624.
Comment on attachment 49873 [details] patch ok.
Landed as r55490.