fix: resolve sqlite database busy errors in tests
- enable WAL journal mode for better concurrent access - increase busy_timeout to 10s - reduce pool_size to 1 to prevent write conflicts Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
51d9504f6b
commit
a44790362a
@ -10,8 +10,10 @@ config :bcrypt_elixir, :log_rounds, 1
|
|||||||
# Run `mix help test` for more information.
|
# Run `mix help test` for more information.
|
||||||
config :simpleshop_theme, SimpleshopTheme.Repo,
|
config :simpleshop_theme, SimpleshopTheme.Repo,
|
||||||
database: Path.expand("../simpleshop_theme_test.db", __DIR__),
|
database: Path.expand("../simpleshop_theme_test.db", __DIR__),
|
||||||
pool_size: 5,
|
pool_size: 1,
|
||||||
pool: Ecto.Adapters.SQL.Sandbox
|
pool: Ecto.Adapters.SQL.Sandbox,
|
||||||
|
journal_mode: :wal,
|
||||||
|
busy_timeout: 10_000
|
||||||
|
|
||||||
# We don't run a server during test. If one is required,
|
# We don't run a server during test. If one is required,
|
||||||
# you can enable the server option below.
|
# you can enable the server option below.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user