Hamzawy's blog

System Testing!!!
By Hamzawy, 13 years ago, In English
Well, Codeforces Beta Round #97 ended. All participants noticed that system testing took too long time to finish.

Me and other contestants wondering why CodeForces starts system testing at the end of the contest.
Will not it be good to start system testing for each submission that passes pretest on another server or something then after contest ends test remaining submissions. 

Even if this solution is not possible or not good. Lets all brainstorm on how to make it faster I think we all will be happy to see our results once contest ends.
  • Vote: I like it
  • +12
  • Vote: I do not like it

13 years ago, # |
  Vote: I like it +1 Vote: I do not like it
for example in last contest some of hack tests added to final tests such that a lot of submissions failed cause of those tests.

also if a problem happened during the contest it's impossible to rejudge all submissions that judged before that.

so this is good idea if the test cases was prepared perfect before contest (that it's very hard work)
→ Reply
  • 13 years ago, # ^ |
    ← Rev. 2   Vote: I like it +1 Vote: I do not like it

    I believe that we can find solutions to this also. For example we can test submission on all test cases even if it failed in one of them, and save which cases passed and which failed. then when hack tests need to be added then only those will be required to be run at the end of the contest.


    In this solution if there were problems in some cases, rejudging them will be very easy as we already have the result of each submission in each test case.
    → Reply
13 years ago, # |
  Vote: I like it 0 Vote: I do not like it
As I noticed yesterday, some submissions including one of mine strangely took a long time (several minutes) to test even when its runtime was only 50ms, while some others with greater runtime started being judged later but still finished earlier. Hope that this round is just an exception and everything will be ok in the next ones.
→ Reply