Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(reopen) Exercise Palindrome Products - Automated tests time out (failing). #1466

Open
stevebeauge opened this issue May 7, 2024 · 2 comments

Comments

@stevebeauge
Copy link

Closely related to #741 and #759 ?

I solved the Palindrome Products in the typescript track.

I encounter what I believe to be timeout on your side. All tests are passing locally, under 20s (the lower value I've been able to reach).

However, the checks on your side are failing with a generic error

An error occurred

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.

Is there anything I can do?

Thanks

Copy link
Contributor

github-actions bot commented May 7, 2024

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.

@github-actions github-actions bot closed this as completed May 7, 2024
@SleeplessByte SleeplessByte reopened this Aug 6, 2024
@SleeplessByte
Copy link
Member

An optimal implementation takes pretty long to execute and thus we skip this test in the test-runner and online editor. If you are running into that error, then the non-optional tests take too long. They should run under 10s, not 20s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants