Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(224)

Unified Diff: LayoutTests/storage/indexeddb/lazy-index-population-expected.txt

Issue 243523003: Fire window.onerror for uncaught IndexedDB errors (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Don't capture full stack unless devtools is visible Created 6 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/storage/indexeddb/lazy-index-population-expected.txt
diff --git a/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt b/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt
index e4a961b3352e1a3285fadb4f04d84570136138e0..d2c42dbb5375dbb8b0dbd96ce6b6d621442bd528 100644
--- a/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt
+++ b/LayoutTests/storage/indexeddb/lazy-index-population-expected.txt
@@ -1,3 +1,6 @@
+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index1': at least one key does not satisfy the uniqueness requirements.
+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index2': at least one key does not satisfy the uniqueness requirements.
+CONSOLE ERROR: line 1: ConstraintError: Unable to add key to index 'index4': at least one key does not satisfy the uniqueness requirements.
Verify edge cases that lazy index population in an IndexedDB implementation might reveal.
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".

Powered by Google App Engine
This is Rietveld 408576698