User is not told what the error is when a runtime error occurs
xmm-t opened this issue · comments
I don't know if the following problem is specific to the Clojure track, or an Exercism problem in general, but anyway...
An error occurred while running your tests. This might mean that there was an issue in our infrastructure, or it might mean that you have something in your code that's causing our systems to break.
Please check your code, and if nothing seems to be wrong, try running the tests again.
This happens so frequently that I don't think it's even necessary to post a reproducible example, and I'm amazed I can't find an issue opened for it already.
What was the error? On which line did it occur? Can I have a stack trace?
Every time this happens, I need to pull my code out of the web editor into a local project and run the tests one by one until I find the one that triggers an error, and then I have to assume that's the same error that was triggered in the web environment.
All of this could be avoided if the error was just passed to the user in the first place.
Telling someone who is learning a new language to "just check your code" is a bit stupid. A new person doesn't know what might be wrong with the code, and with the level of information given I wouldn't be surprised if seasoned developers didn't know either.
Just pass the error to the user so they know what to fix.
That message is the result of an infrastructure issue and not with the Clojure track, and the devops team has been busy recently, so hopefully we won't see any more of these. Sorry for the confusion.