Hello, I’m having a frustrating experience with the Unison track where despite all the tests passing locally the first time I submit my exercise the test runner will time out.
At this point I’m skeptical whenever I see a timeout that the issue is due to inefficiency in my code. I’ve submitted my solution for Allergies 10x now and it continues to fail despite the solution being rather simple.
Additionally, each time I submit the test runner the UI displays “Pending” followed by “Passed” only to flip to “Failed” a second later.
It feels bad to appear as if I’ve done 10x+ iterations when I’m really still on my first one.
Ideally, if I’m submitting the same solution w/ the past failure due to a timeout I’d like to have it retry the test w/o burning a new iteration.
I was having similar problems with the Swift track, which I resolved by giving up. My impression is that it must be successfully validating the solution, but timing out as it tries to do something else.
Hi @averon, I’m a Unison track maintainer here! Apologies for the slowness in the Unison test runner! I can see if there’s anything amiss with the Unison executable, but it might be some combination of network and infrastructure latency that is beyond my ability to fix. Sometimes to check if my solution is timing out legitimately, I’ll copy the test and implementation locally to a .u suffixed file and run them against a local installation of the UCM. I realize that may not be a workable fix for everyone though! In any case, thanks for giving Unison a try!