Tests

Sliding Sync: Easier to understand timeline assertions in tests (#17511) #2524

Job	Run time
changes	1s
check-lockfile	9s
lint-crlf	4s
lint-newsfile	0s
lint-clippy	2m 43s
check-sampleconfig	1m 0s
lint	50s
check-schema-delta	41s
lint-clippy-nightly	2m 40s
lint-pydantic	39s
lint-readme	8s
lint-rustfmt	2m 20s
Typechecking	1m 25s
linting-done	2s
calculate-test-jobs	8s
trial-olddeps	7m 31s
complement (monolith, SQLite)	13m 11s
portdb (3.8, 11)	2m 51s
trial-pypy	0s
complement (monolith, Postgres)	13m 50s
portdb (3.11, 15)	3m 22s
complement (workers, Postgres)	21m 21s
cargo-bench	0s
cargo-test	0s
sytest (focal)	8m 19s
trial (3.8, sqlite, all)	5m 26s
sytest (focal, postgres)	10m 6s
trial (3.9, sqlite, all)	11m 0s
sytest (focal, multi-postgres, workers)	13m 9s
trial (3.10, sqlite, all)	11m 2s
sytest (focal, multi-postgres, workers, asyncio)	19m 6s
trial (3.11, sqlite, all)	7m 26s
sytest (focal, asyncio)	10m 8s
trial (3.12, sqlite, all)	4m 21s
sytest (focal, postgres, asyncio)	11m 46s
trial (3.8, postgres, 11, all)	12m 0s
sytest (testing, postgres)	10m 44s
trial (3.12, postgres, 16, all)	11m 16s
trial (3.8, sqlite)	4m 35s
export-data	2m 3s
tests-done	2s
	3h 47m 25s

Provide feedback