Has it changed since last year?
Now I can't run it for last year's tasks (Judge return code: 255)
It works fine for this year's tasks.
Has it changed since last year?
Now I can't run it for last year's tasks (Judge return code: 255)
It works fine for this year's tasks.
# | User | Rating |
---|---|---|
1 | tourist | 3757 |
2 | jiangly | 3647 |
3 | Benq | 3581 |
4 | orzdevinwang | 3570 |
5 | Geothermal | 3569 |
5 | cnnfls_csy | 3569 |
7 | Radewoosh | 3509 |
8 | ecnerwala | 3486 |
9 | jqdai0815 | 3474 |
10 | gyh20 | 3447 |
# | User | Contrib. |
---|---|---|
1 | maomao90 | 171 |
2 | awoo | 165 |
3 | adamant | 164 |
4 | TheScrasse | 159 |
5 | maroonrk | 155 |
6 | nor | 153 |
7 | -is-this-fft- | 152 |
8 | Petr | 147 |
9 | orz | 146 |
10 | pajenegod | 145 |
Name |
---|
OK, we don't need interactive runners for last year's tasks (like "python testing_tool.py ./a"). This year we need it (like "python interactive_runner.py python testing_tool.py 0 -- ./a").