Probably not an issue ;-)

me three

I just fixed the Go version. Let me know if it's still failing.

I've just tried it in Go: 3010 ms, 40 really small arrays in the random tests. So any timeouts are probably generic Codewars timeouts (which are not too rare for some of the languages, unfortunately) or it's your solution.

Using Golang, the system-generated full test suite times out 99% of the time before any code executes. The sample tests pass and take little time to run. The sample tests do not have auto-generated test cases. There is a problem with your auto-generated test cases.

"There are no performance tests going on at all..."

Golang, and I didn't say there are performance tests running. Running the full test suite times out 99% of the time before any of my code executes. 0ms code execution time, which suggests your code that is generating the test cases is timing out before my code executes.

Thanks for closing the issue, btw, before even getting an answer to your own questions.

@GiacomoSorbi

You need to beef up the random tests.

Which language are you talking about? There are only 40 random tests with less than 100 elements each. There are no performance tests going on at all.

It takes so long for the system to generate the random tests that the whole thing consistently times out before the tests can even execute. Why are there so many randomly generated tests?

I wrote a solution and all the sample tests pass. When I submit my final answer, the server never runs the code. It always times out.

Golang still broken after three weeks. BOO