Closed a-kinder closed 4 years ago
This is a low level PG error. Do you happen to be dropping tables or re-running migrations within your tests?
We do have a migration rollback test, and one test using drain_queue
was running asynchronously, will close this issue assuming that will fix it. Thanks!
Environment
Current Behavior
Expected Behavior
During tests, this error is observed intermittently when using Oban.drain_queue, both in synchronous and asynchronous tests. It seems to be some kind of race condition with the
status
enum, possibly due to the select and update in a single transaction inOban.Query
?