1. Oleg Oshmyan
  2. Upreckon
  3. Issues
Issue #3 resolved

A checker outputting Cyrillic characters kills Upreckon

Aleksejs Popovs
created an issue

{{{ D:\Popov\26.06>upreckon -x 01: 0.000/2.000 s, 1/1, OK (N=7 K=3) 02: 0.016/2.000 s, 1/1, OK (N=15 K=20) 03: 0.016/2.000 s, 1/1, OK (N=176 K=1) 04: 0.016/2.000 s, 1/1, OK (N=1 K=1) 05: 0.016/2.000 s, 1/1, OK (N=2 K=1) 06: 0.000/2.000 s, 1/1, OK (N=9 K=3) 07: 0.000/2.000 s, 1/1, OK (N=9 K=11) 08: 0.000/2.000 s, 1/1, OK (N=11 K=6) 09: 0.078/2.000 s, 1/1, OK (N=4369 K=257) 10: 0.421/2.000 s, 1/1, OK (N=9797 K=101) 11: 0.000/2.000 s, 1/1, OK (N=10000 K=10000) 12: 0.000/2.000 s, 1/1, OK (N=7 K=1) 13: 0.000/2.000 s, 1/1, OK (N=15 K=1) 14: 0.000/2.000 s, 1/1, OK (N=14 K=3) 15: 0.000/2.000 s, 1/1, OK (N=17 K=4) 16: 0.016/2.000 s, 1/1, OK (N=23 K=9) 17: 0.016/2.000 s, 1/1, OK (N=32 K=1) 18: 0.000/2.000 s, 1/1, OK (N=55 K=6) 19: 0.000/2.000 s, Traceback (most recent call last): File "C:\Python31\Scripts\upreckon", line 80, in <module> real, max = problem.test() File "C:\Python31\lib\site-packages\upreckon\problem.py", line 209, in test say('%g/%g, %s' % (granted, case.points, verdict)) File "C:\Python31\lib\encodings\cp866.py", line 19, in encode return codecs.charmap_encode(input,self.errors,encoding_map)[0] UnicodeEncodeError: 'charmap' codec can't encode characters in position 22-23: character maps to <undefined> }}}

{{{ D:\Popov\26.06>c < tests\Input19.txt 1+2+2(1+2+2)(2+2+2) D:\Popov\26.06>c < tests\Input19.txt > ans.out

D:\Popov\26.06>checker tests\Input19.txt ans.out tests\Answer19.txt WA Неверный ответ N=63 K=2 Found length 21 instead of 19 }}}

Comments (5)

  1. Aleksejs Popovs reporter

    My task configuration is attached.

    It includes testconf.py, all the tests, pascal source & Win32 binary for the checker, pascal source & Win32 binary for a solution that fails test 09 (and possible others, too). If you want to compile the checker, you'll have to Google for 'testlib.pas' and put it in the same directory as the source file for the checker.

  2. Oleg Oshmyan repo owner

    Thanks! I have now fixed this in the default branch. I have not yet decided whether to backport this fix to 2.03, since it kind of breaks compatibility with existing (as if) callable output validators.

  3. Oleg Oshmyan repo owner

    Yeah, and today—very soon after I announced the release of 2.04.0—it suddenly occurred to me that I didn’t actually have to break compatibility with existing callable output validators. So I fixed that and moved the 2.04.0 tag in proper bad software version number management fashion. That’s a lot of adjectives and nouns in a row.

  4. Log in to comment