summaryrefslogtreecommitdiffstats
path: root/comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js
diff options
context:
space:
mode:
Diffstat (limited to 'comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js')
-rw-r--r--comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js12
1 files changed, 12 insertions, 0 deletions
diff --git a/comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js b/comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js
new file mode 100644
index 0000000000..f60c1dd29e
--- /dev/null
+++ b/comm/mailnews/db/gloda/test/unit/test_nuke_migration_from_future.js
@@ -0,0 +1,12 @@
+/**
+ * There are actually two ways the nuke migration can be invoked. From
+ * a database too far from the future, and too far from the past. This
+ * one is the future one. We must keep ourselves safe from time-traveling
+ * grandchildren!
+ */
+
+/* import-globals-from test_nuke_migration.js */
+load("test_nuke_migration.js");
+
+// pick something so far forward it will never get used!
+BAD_DB_VERSION_TO_USE = 100000000;