Leetcode's Judge System has some server side bugs

I'd like my rating to not be updated for Biweekly Contest 24 for the two following reasons:

Reason 1

As shown in the these two screenshots:
image
image

The judge system sends a Time Limit Exceeded for submissions that have a 12ms execution time. I have never seen any competitive programming platform giving TLE results with an execution time inferior to one tenth of a second. If this is the intended behaviour on LeetCode's side, then let it be. I made one more optimization on that code which ended up Accepted with a runtime of 0ms. Anyway the second reason should still be enough to either compensate my penalty time or not update my rating after this contest.

Reason 2

As shown in this screenshot:

image

My code was submitted and the judge system's output is "Wrong Answer" for the test case

"1000"
10

However, when I click "Run Code" on that exact same test case, with the exact same code, the output of my code is the expected one, i.e. 0. Basically that means either one of two things:

  • My code gives the right answer but the judge system is bugged in some way that it does not execute the code in the same environment when clicking "Run Code" or "Submit"
  • My code is wrong, in which case I did not get a correct feedback from LeetCode, which means I did not play the contest in the same conditions and with the same tools as the other participants, making my participation in the contest invalid.

I hope everything is clear enough. I can certify that, in all these screenshots, both outputs were given by the exact same code (and I'm pretty sure that can be checked on LeetCode's side), and I even tried them all several times just in case it was an unreproducible bug, adding to my wrong submission penalty time. My LeetCode rating is rather important as I plan some job interviews in a near future which is why I either want to not be rated for that contest, or my ranking to be recomputed for that specific contest as if these bugs did not happen.

Thanks for reading,

brurrito

Comments (1)