oittuser, as one can guess, is just oitt but with user CPU time instead of instrucion count.
The difference from oireal is quite small, but this should allow s2j to be used in place of sioworkers' DetailedUnprotectedExecutor, allowing a significant security upgrade without having to modify problems' time limits at all.
The sys CPU time is also stored, as it might be useful in the future (maybe in sth like a human-full output format?).
oittuser
, as one can guess, is justoitt
but with user CPU time instead of instrucion count. The difference fromoireal
is quite small, but this should allow s2j to be used in place of sioworkers'DetailedUnprotectedExecutor
, allowing a significant security upgrade without having to modify problems' time limits at all. The sys CPU time is also stored, as it might be useful in the future (maybe in sth like ahuman-full
output format?).human
provides an oiejq-inspired human-readable output. Resolves https://github.com/sio2project/sio2jail/issues/8.Sample outputs of the latter: (here the first line is a program's stdout)