Once again, the problem of test cases being extremely weak was highlighted in the FEBRUARY long challenge. The problem “Call centre Scheduling” was probably a good one but it contained weak test cases. Even my greedy solution which I think could fail on some corner cases passed easily. You can have a look at My solution .
The more weird think was that this solution also passed the test cases which actually doesn’t implement any algorithm, just prints out “yes” and “no” randomly. The interesting thing is that the program uses “srand((unsigned)time(NULL));” which actually generates random numbers according to the system time, meaning the same solution may fail sometimes but gets AC other times.
Really it was annoying to see such solutions getting AC in such renowned contests. I hope Codechef looks into much matters carefully. I rejudge of the problem with Strong test case data would be the best solution. I would not mind even my solution getting WA after that but it would do justice to others as well.
Looking forward for some quick action.