On Monday the 2nd of June the Swift track will enter maintenance at 10:00 CEST. The track (and its tooling) will become unavailable or partially unavailable for a period of time. I can’t give out an ETA.
Why is the a need for maintenance? Good question, I have since November worked on bringing Swift 6 to the Swift track and that work will release on Monday. The thing is that the new content is not compatible with the old architecture at all, this means that all exercises and tooling has to be changed at the same time. The approach which I am planning to take is first pushing the test runner (which takes around 10 min) and then start to slowly update the exercise. Both for the servers and for testing purposes (so I can see early if a rollback would be needed. I have done quite a bit of testing so shouldn’t be an issue, however performance tests are a bit harder to preform on my own hardware).
My goal with highlighting this is mostly so folks don’t get confused if the test runner suddenly stops working. And I also want to mention once again that we are dropping Swift 5, which I have already mentioned: Swift 6 blog post - Exercism - Exercism.