You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Working solution to PasswordChecker failing on Exercism infrastructure #1371
Since I seem to be the first one that tried to solve the (quite) new PasswordChecker exercise, I think I should communicate the problem I had. Although I had all the tests passing in my IDE (Visual Studio Insiders), when submitting my solution to exercism via the CLI it failed (I tried it 5 times) with the message "An error occurred while running your tests. This might mean that there was an issue in our infrastructure, ..."
I cannot find anything undesirable in my code (you can watch it in the Community solutions, it is the first one published there), so perhaps the issue is really in the infrastructure.
If I can help with anything like more information (sorry, I don't know anything about exercisms infrastructure or where I would have to look to see if something is broken or not set up correctly) or if the problem has been solved, please contact me.
At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.
This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!
If you're interested in learning more about this auto-responder, please read this blog post.
Activity
github-actions commentedon Feb 24, 2026
Hello. Thanks for opening an issue on Exercism 🙂
At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.
This issue will be automatically closed. Please use this link to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!
If you're interested in learning more about this auto-responder, please read this blog post.
ErikSchierboom commentedon Feb 24, 2026
This must be due to the slowness of the test runner which is hard to fix unfortunately