feat: use ATUIN_TEST_SQLITE_STORE_TIMEOUT to specify test timeout of SQLite store (#1703)

Low-end devices like RISC-V SBCs are sometimes too slow to initialize SQLite in 0.1s. Option to specify a higher value allows check to pass on such devices with relaxed restrictions.

1 files changed, 3 insertions, 3 deletions

diff --git a/atuin-client/src/record/sync.rs b/atuin-client/src/record/sync.rs
index e3644371..02c53d44 100644
--- a/atuin-client/src/record/sync.rs
+++ b/atuin-client/src/record/sync.rs
@@ -324,7 +324,7 @@ mod tests {
 
     use crate::record::{
         encryption::PASETO_V4,
-        sqlite_store::SqliteStore,
+        sqlite_store::{test_sqlite_store_timeout, SqliteStore},
         store::Store,
         sync::{self, Operation},
     };
@@ -351,10 +351,10 @@ mod tests {
         local_records: Vec<Record<EncryptedData>>,
         remote_records: Vec<Record<EncryptedData>>,
     ) -> (SqliteStore, Vec<Diff>) {
-        let local_store = SqliteStore::new(":memory:", 0.1)
+        let local_store = SqliteStore::new(":memory:", test_sqlite_store_timeout())
             .await
             .expect("failed to open in memory sqlite");
-        let remote_store = SqliteStore::new(":memory:", 0.1)
+        let remote_store = SqliteStore::new(":memory:", test_sqlite_store_timeout())
             .await
             .expect("failed to open in memory sqlite"); // "remote"