It seems to me that the running time of a Kata includes the times it takes to compile the code. I've noticed for Factor, that compilation for sample code can take 1.5-2 seconds, while actual execution takes less than a millisecond.
I've run into a Kata that will time-out for no obvious reason, but I suspect it has to do with the way the test code is structured, and its compilation time is counting towards timeouts. As it is a timeout error, I also am unable to see partial results, including time it takes to run particular tests. I can therefore not determine where the exact error is.
Either do not count compilation time as part of the user execution time for timeouts, or in case of a timeout, show more detailed information on the timing of the testcases already executed before the timeout.
It seems to me that the running time of a Kata includes the times it takes to compile the code. I've noticed for Factor, that compilation for sample code can take 1.5-2 seconds, while actual execution takes less than a millisecond.
I've run into a Kata that will time-out for no obvious reason, but I suspect it has to do with the way the test code is structured, and its compilation time is counting towards timeouts. As it is a timeout error, I also am unable to see partial results, including time it takes to run particular tests. I can therefore not determine where the exact error is.
Either do not count compilation time as part of the user execution time for timeouts, or in case of a timeout, show more detailed information on the timing of the testcases already executed before the timeout.