MikeMirzayanov Please look into this.
There might be some issue with the Checker.
I'm getting denial of judgement verdict in the problem 1221A - 2048 Game.
I'm getting this verdict even on the submissions which earlier got Accepted.
Accepted Solution
Similar Solution which got Denial of Judgement Verdict
→ Pay attention
→ Streams
→ Top rated
| # | User | Rating |
|---|---|---|
| 1 | tourist | 3985 |
| 2 | jiangly | 3814 |
| 3 | jqdai0815 | 3682 |
| 4 | Benq | 3529 |
| 5 | orzdevinwang | 3526 |
| 6 | ksun48 | 3517 |
| 7 | Radewoosh | 3410 |
| 8 | hos.lyric | 3399 |
| 9 | ecnerwala | 3392 |
| 9 | Um_nik | 3392 |
→ Top contributors
| # | User | Contrib. |
|---|---|---|
| 1 | cry | 169 |
| 2 | maomao90 | 162 |
| 2 | Um_nik | 162 |
| 4 | atcoder_official | 161 |
| 5 | djm03178 | 158 |
| 6 | -is-this-fft- | 157 |
| 7 | adamant | 155 |
| 8 | awoo | 154 |
| 8 | Dominater069 | 154 |
| 10 | luogu_official | 150 |
→ Find user
→ Recent actions
Codeforces (c) Copyright 2010-2024 Mike Mirzayanov
The only programming contests Web 2.0 platform
Server time: Dec/22/2024 20:28:39 (l2).
Desktop version, switch to mobile version.
Supported by
I think the checker is smart, not faulty. lol... basically, it will not accept your exact code more than once.
The error doesn't seem like to be caused because of duplicate source code.
As we can see the error message on the submission page is about the verdict being crashed.
Verdict: CRASHEDTried resubmitting tejustiwari's code from my account: https://mirror.codeforces.com/contest/1221/submission/96810532
Submitted a new code: https://mirror.codeforces.com/contest/1221/submission/96810849
But still seeing
Denial of judgementfor both.Re-tagging MikeMirzayanov for visibility :)
Just submitted a solution to a practice question from another contest. It passed. — https://mirror.codeforces.com/contest/1436/submission/96811137
Yes Ingenious , the checker is smart, but sadly you aren't. The codes are not exactly same.
I've changed an endl to "\n" keeping the logic same but codes different.
Anyways they've resolved this error now ! Thanks Mike !