Hi friends, I’m working on a contribution to Finch and am having a hell of a time debugging an unexpected process exit that’s causing a test to fail. Code being tested Test that’s failing The code being tested is rather unfinished and very much a work-in-progress, but I wanted to have a baseline…

The message looks a lot like the symptom from this issue: https://github.com/PSPDFKit-labs/bypass/issues/120 This could be happening when the Task terminates while still waiting for a reply from Bypass, causing the Bypass process to crash and taking the test process down along with it. You could …

That looks really promising. I cloned Bypass and changed the dep to a local path-based one and then tried fixing the line referenced in that issue and removing it altogether, both to no avail. It does seem likely that it’s taking down the Bypass server somehow.

That was a good idea. ......................................self: #PID<0.1343.0> bypass: #PID<0.1344.0> async req pid: #PID<0.1360.0> finch: #PID<0.1357.0> *DBG* <0.1344.0> got {'DOWN',#Ref<0.1067949558.531890179.24259>,process, <0.1363.0>,shutdown} *DBG* <0.1344.0> new…

I know it’s a bit late, but I have also encountered this problem, and I was able to resolve it by calling the Bypass.down function before the end of the test: Bypass.down(bypass) I hope this helps someone in the future.

Bypass.down(bypass) for us didn’t work. However, what works is “overriding” the on_exit for the bypass so that it doesn’t try to verify the expectations. on_exit({Bypass, bypass.pid}, fn -> :ok end) Some notes on my investigation: In order to reproduce the issue we could do the following: bypa…