search

icnhoukdsiih / testlib

Automatically exported from code.google.com/p/testlib
0 stars 0 forks source link

PC_BASE_EXIT_CODE = 0 #10

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create checker for a problem with partially correct results
2. Run it using Testsys
3. Get JE on most of the tests

Testsys expects the PC exit codes be in range 50..250, but we'll get 0..200. 
This range also intersects with the range where lie WA, PE etc.
AFAIK, PCMS uses something similar. I don't know about ejudge, however i doubt 
it uses 0 as the base also.

Original issue reported on code.google.com by jps...@gmail.com on 29 Nov 2010 at 9:29

GoogleCodeExporter commented 8 years ago 
It should be investigated about exit codes in pcms2 and other systems. Also I 
afraid, changes in PC_BASE_EXIT_CODE will affect backward compatibility.

Original comment by mirzayan...@gmail.com on 18 Dec 2010 at 5:47

GoogleCodeExporter commented 8 years ago 
At least for Testsys, PC_BASE_EXIT_CODE should be 50 instead of 0.

On All-Russian School Training Camps, in order to fix this issue, we usually 
patch our local testlib.h, hoping for forward compatibility, instead of using 
the wrong value.

So, changing PC_BASE_EXIT_CODE to 50 (in #ifndef EJUDGE section) would not 
break compatibility at least for us, and would be a technically superior 
solution compared to leaving things broken in library code for hypothetical 
backward compatibility.

Original comment by gass...@gmail.com on 1 Dec 2011 at 11:23

GoogleCodeExporter commented 8 years ago 
PC_BASE_EXIT_CODE=50 in case of defined TESTSYS

Original comment by mirzayan...@gmail.com on 29 Dec 2011 at 4:53