mirror of
https://github.com/LemmyNet/lemmy.git
synced 2024-11-05 04:00:02 +00:00
600ae662a5
Since DB tests execute diesel migrations automatically, concurrent execution causes flaky failures from simultaneous migrations. This can be worked around using `cargo test --workspace -- --test-threads=1`, which is what the CI config does, but this is not intuitive for newcomer developers and unnecessarily slows down the test suite for the majority of tests which are safe to run concurrently. This fixes this issue by integrating with the small test crate `serial_test` and using it to explicitly mark DB tests to run sequentially while allowing all other tests to run in parallel. Additionally, this greatly improves the speed of `cargo test` by disabling doc-tests in all crates, since these are aren't currently used and cargo's doc-test pass, even when no doc-tests exist, has significant overhead. On my machine, this change significantly improves test suite times by about 85%, making it much more practical to develop with tools like `cargo watch` auto-running tests.
13 lines
348 B
TOML
13 lines
348 B
TOML
[package]
|
|
name = "lemmy_db_views_moderator"
|
|
version = "0.1.0"
|
|
edition = "2018"
|
|
|
|
[lib]
|
|
doctest = false
|
|
|
|
[dependencies]
|
|
lemmy_db_queries = { path = "../db_queries" }
|
|
lemmy_db_schema = { path = "../db_schema" }
|
|
diesel = { version = "1.4.5", features = ["postgres","chrono","r2d2","serde_json"] }
|
|
serde = { version = "1.0.123", features = ["derive"] }
|