I wonder what happened behind the scene during "pending system testing". It always takes so long...
# | 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 |
# | 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 |
I wonder what happened behind the scene during "pending system testing". It always takes so long...
Name |
---|
in my opinion, jury is appending hacks to the tests...
Right, that definitely. And maybe other stuff like skipping obvious cheating submissions?
Are the successful hacks really added to the tests? I did one during last match and it did not appear in final tests.
As far as I know, it is jury's decision to add or not to add an specific hack. I think they add a hack if the hacked solution would got AC with the current tests. I remember Gerald saying that in some post.
If they were all added, it could be automated and then there wouldn't really be any need for the long time that Pending system testing takes, right?
I think almost successful hacking tests aren't added to the system tests, as there can be many successful hacks (for example, in Codeforces Round 263 (Div. 2), problem B had 1193 successful hacks, but the final tests had only 41 tests).
I think when coding phase was ended, there are still some submissions and hacks in queue. Pending system testing phase will evaluate them.
That is really small amount of time compared to usual lasting time of "pending system testing" phase...