Run the load tests on Postgres, as production runs #139
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The load tests (#133) run their scratch daemon on SQLite, so their numbers carry SQLite's one connection (#136) and its locking, not what production sees on Postgres 18. The harness wipes its SQLite files before each run; on Postgres it would need a database of its own, emptied first (a throwaway container, or DROP SCHEMA public CASCADE), and a way to reach it from wherever the tests run.
Done in
bbdcbe2: node tests/load/run.js --postgres runs the daemon in IPX_TEST_DATABASE_URL (ipodderx_test on production's server, as ipodderx, in /src/.envrc from ipx.env), schema ipx_load made afresh each run, refusing any database not named *_test, with ANALYZE after seeding. Budgets are per database. All four pass on both. Running it found #140.