It is odd that the tests run so slowly, but I’m not sure that’s redwood’s problem yet.
When I run with postgres in docker locally, the full suite of mostly generated tests, about 92 of them, completes in about 14 seconds.
When my TEST_DATABASE_URL points to postgres on AWS or on Railway, some tests are taking the ballpark of 8 seconds (hence the timeout at 5s).
The tests are pretty lightweight. I assumed it was some connection pool or similar config error I made.
What makes me think it could be something in rw is that it happens both on Railway and AWS.
Further weirdness, it has run successfully on Github Actions.
I thought it could be my network, but my bandwidth is good (E.g. - streaming video up and down, often multiple streams at once is normal and fine) and these tests are fetching like 2 rows of 8 columns of data or less.
Maybe something in the scenario seeding is blocking, or there’s just enough network latency to introduce a race condition that I don’t see locally?