[General: Slow Testing Exercises] Exercises that have Slow Running Tests that Time Out in the UI

[BethanyG]

This is an open issue for Exercises that have reasonable solutions that "time out" under test in the UI.

To be clear -- this is not for exercises that time out due to inefficient code, but ones that reasonably pass in in the runner locally or in docker, but take too long in the UI once the containers are spun up and configured.

For now, we need to flag these as "slow", so that they don't run on the website and unnecessarily take up resources.

Please add any additional exercises you think fit this criteria. Thanks!

• [ ] Palindrome Products
• [ ] Pythagorean Triplet

[BethanyG]

As talked about in a previous Slack discussion, we should add notes to these exercises to the effect:

Note: your solution must complete in under 10s for the tests to pass on the online editor and exercism website.

[BethanyG]

Link to issues that also deal with this problem: Elixir 817 & exercism docs 169. As suggested in the Elixir issue, since PyTest (our runner) supports a skip, we could perhaps turn off the data intensive tests, rather than the whole exercise, and add an append to the exercise to describe to the student what do to to run those "heavy" tests.

IIRC, the tests for these exercises are auto-generated, so we may or may not need to play with tests.toml and/or the JinJa2 template associated with them. We'll cross that bridge once we have a set to look at. 😄

Link to the docs that cover track config Link to practice exercise config