Weird timing errors should be fixed

by bbi5291 on Aug 20, 2014 - 4:38:55 am UTC
  • (1/0)
CPU time usage is now reported more accurately, so you won't see 4.5 s reported if your program TLEs on a 5 second limit. (Actually the measured time may be something like 4.999 s, in which case it gets rounded up to 5.000. But the point is that time is reported more accurately now.)

Also, if the time limit is 0.5 s, and your program uses 0.6 s, this used to not be considered a TLE, but this was a bug, which is now fixed.

Comments (Search)

It's quiet in here...