From d0a89afa934b314a990d71e9ac6cd6870a2689eb Mon Sep 17 00:00:00 2001 From: manuel Date: Sat, 26 Oct 2024 12:14:21 +0800 Subject: [PATCH] Update JOJ3 Configuration For TAs --- JOJ3-Configuration-For-TAs.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/JOJ3-Configuration-For-TAs.md b/JOJ3-Configuration-For-TAs.md index 595a404..1e86291 100644 --- a/JOJ3-Configuration-For-TAs.md +++ b/JOJ3-Configuration-For-TAs.md @@ -111,14 +111,22 @@ the next table is defined. - `limit.stdout [int]`: default `stdout` size applicable to the stage in kB (default: `4`) - `limit.stderr [int]`: default `stderr` size applicable to the stage in kB (default: `4`) +### Online judge options + +While online judge stages work in a similar way as other stages, they often feature more than one step. For instance, while a compilation or code quality stage +is composed of a single step where the code is compiled or analysed, an online judge stage can features many steps, each corresponding to a test-case. +Therefore, on-top of the regular stage options, online-judge stages can be adjusted at "step level ", ie. for each test-case. Any online-judge stage *must* feature the keyword `judge`, eg. `judge`, `judge-base`, `asan-judge` are all valid online-judge stage names while `oj`, `run-base`, and `asan` are not. -An online-judge stage is configure as any other stage, ie. using the above options, but can feature an -extra parameter: +The following extra option is available for online-judge stages: - `skip [array of string]`: list of test cases to skip for this stage (default: `[ ]`) +For each step, ie. test-case, the following configuration can be adjusted: +- `limit.cpu [int]`: maximum running time for the stage in sec (default: `4`) +- `limit.mem [int]`: maximum amount of RAM allowed for the stage in MB (default: `4`) + ### Parsers