You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
someone in the thread linked above said: "the error means that a db query is live when the test is torn down, in our case it was due to some of our liveview tests clicking a submit button that caused a push_patch to happen in a live_component rather than the parent liveview,"
When running mix test with --trace` and a slowdown on exit, we can see where the postgrex timeout's are showing up.
Here are the culprits, as text:
BikeBrigadeWeb.CampaignLiveTest [test/bike_brigade_web/live/campaign_live_test.exs]
* test Show with riders Can assign a rider to a task [L#199]18:06:02.780 [error] Postgrex.Protocol (#PID<0.479.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.961.0> exited
* test Show with riders Can unassign a rider from a task [L#224]18:06:03.868 [error] Postgrex.Protocol (#PID<0.488.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.981.0> exited
BikeBrigadeWeb.CampaignSignupLiveTest [test/bike_brigade_web/live/campaign_signup_live_test.exs]
* test Show Rider can signup for a task [L#175]18:06:16.499 [error] Postgrex.Protocol (#PID<0.482.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0.1256.0> exited
I think I'll come back to this a bit later, as it doesn't really constitute a failing test and I think is low priority.
Every time I run tests this spews:
And I have just ignored it forever because it's a skipped test.
Let's fix it!
The text was updated successfully, but these errors were encountered: