Thanks, there are 31 random tests of each category.

late answer, but.... no, it's not the good way to solve this.

@ZED.CWT, thanks for paying attention to me. Luckily, I was able to solve this issue by turning off clang optimizations via #pragma clang optimize off. It reduced compile time a lot and all tests now pass like a breeze. Though, I think it's pretty fair. You probably have seen how bloated my original solution is, so there's no wonder why clang can't compile and optimize it fast enough, haha

@MikChan
So you currently timeout no matter how many times you try submit? How about the sample tests? Or empty the test code to see how long does it take to compile.
Maybe you could raise an issue on github and PM your code to CW maintainer to investigate the bottleneck

Haha, I have the same problem right now. I used to bypass it via using gcc, because it was compiling faster for some reason, but seems like it got removed. That's sad.

Um.. What i meant by compliling is time consumed by clang to compile your code + test suite
Anyway, congratulations!
Glad that you had fun here

Normally it is consumed by compiling
The reference solution passes the full test under ~618ms also takes ~12s in total

fixed

print it to the console, to see what it is. Just means your code doesn't handle properly some situation.

So what is diffrent in test 73? I am also stuck there :-(
I measured the time of solving all the previous tests in my computer and its ~0.6s...

188. Not so far... ;)

I just tried some solutions and they pass the tests successfully. So the problem is on your side. Are you sure you don't get a buffer limit error rather than a time out, when you print to the console? Either way, put a global counter to not print before you reach the tests you're interested in.

You can post your code if you want (don't forget the spoiler flag)