Is there actually any way of seeing lets say test case 91 , because usually it just shows like less then the first 50
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3773 |
3 | Radewoosh | 3646 |
4 | ecnerwala | 3624 |
5 | jqdai0815 | 3620 |
5 | Benq | 3620 |
7 | orzdevinwang | 3612 |
8 | Geothermal | 3569 |
8 | cnnfls_csy | 3569 |
10 | gyh20 | 3447 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | awoo | 161 |
2 | maomao90 | 160 |
3 | nor | 157 |
4 | atcoder_official | 156 |
4 | cry | 156 |
6 | -is-this-fft- | 155 |
7 | maroonrk | 154 |
8 | adamant | 153 |
9 | Um_nik | 151 |
10 | djm03178 | 146 |
Is there actually any way of seeing lets say test case 91 , because usually it just shows like less then the first 50
Название |
---|
I did it once. I output that value in my answer thus, I could see where my code is failing. Here is how I did it 227046320.
Just giving more clarity to Duelist1234, you have to output the input value for that particular test case and see the wrong answer reason after submitting. It shows some X printed instead of the answer . That X is actually your input for that particular test case.
no, codeforces don't support downloading the whole testing data of a problem.
usually, it's easier to rewrite your code and rethink the edge cases. but if you really need the failed test case, you can hard code a condition to catch the failing test case and only output its data.
i test cases while high