Tests are updated

fixed

yw!

:-)

Running your performance test with my solution on CW server:

         987670 function calls (290555 primitive calls) in 0.623 seconds

   Ordered by: standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    0.623    0.623 <string>:1(<module>)
        1    0.000    0.000    0.623    0.623 main.py:3(performance_test)
       17    0.000    0.000    0.623    0.037 solution.py:1(balanced_parens)
697130/15    0.593    0.000    0.623    0.042 solution.py:6(dfs)
        1    0.000    0.000    0.623    0.623 {built-in method builtins.exec}
   290519    0.030    0.000    0.030    0.000 {method 'append' of 'list' objects}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

With my solution, full test suite runs in ~3s. As far as I noticed, n can go up to 12.
If you are getting timeouts for n=0..12, there's some more work for you ;)

Good catch; found the source of the bug and fixed it for both JS and Python.

and yet, that's what you actually did... x)

mmmmh.... :/

Sounds like evk heard you

Last Seen:Sep 2019

;o

lol... Sounds like evk heard you: the completion time just dropped to 2s... x/

=> evk: it's not heavy enough, now.

1. dijskstra is'nt the most efficient algo here
2. tests have always been heavy, in this kata
3. I checked my two solutions: they both run in the time limit (10,2s and 11,2s)
4. 8s for the tests means that half or more of this time is spent generating the mazes, meaning the warrior can still pass the tests with a reasonnable/efficient approach
5. again, this is not a kata issue, but a runner issue. So it's still annoying, yes, but shouldn't be handle on this side (kata side) as long as the the kata is still completable.

Sounds pretty appropriate for a 4 kyu, imo. ;)

not a kata issue (it's a runner problem due to some of the last updates). Moreover, the tests are still passable that way, so definitely not an issue.