Is anyone facing timeout issues on Swift track exercises?
I’m running into a timeout error on the Meetup exercise.
My code runs fine in other Swift environments (like Xcode), but on Exercism Web, it keeps timing out, even though there’s no infinite loop or heavy computation.
I’ve had similar problems on the Queen Attack exercise too.
The runner says:
Build complete! (10.68s)
-but then just hangs and doesn’t let me submit.
Is this a known issue with the Swift test runner or setup on Exercism?
Would really appreciate any help, suggestions, or confirmation if others are seeing this too.
On Queen Attack, it times out whether I use an empty file or the example solution. That suggests there might be an issue with the test runner results being reported back to the website.
1 Like
There has been a lot of work on the Swift track recently, and I believe that the maintainer is still working through the odd issue with version mismatch and tooling changes. These might be some of them, but not totally sure.
cc: @Meatball
2 Likes
So generally Swift is a quite slow language when it comes to compiling. Which in turns means that timeout are quite hard to circumvent. I have taken some measurements to try to improve performance but it is just so much that I can do. What I can tell is that queen attack had a bug which was fixed yesterday. So if you go to the tests tab, make sure it says import Testing and not import XCTest. As for meetup, I think due to it having a ton of tests it makes the execution take a bit too long. I will check if there is anything I can do about it, but otherwise I recommend reruning a few times, that usually does the trick.
I will also start exploring changing the build system but that wont come for a few months at least.
2 Likes
FWIW I saw a lot of timeouts on the JS track (from CLI) as well, so I wouldn’t be surprised if it has nothing to do with the track test-runner itself.
2 Likes
@BNAndras yeah that checks out, I tried the example solution too and same thing happened.
@Meatball good to know Queen Attack was fixed. As for Meetup, yeah I’ll try running it a few more times and see what happens. Appreciate you looking into it!
Yeah, I’ve been experiencing the same issue. In pretty much every exercise I submit I get the test timeout error. However, if I keep trying to run the tests in the online editor, they eventually pass and I’m able to complete the exercise.