JOJ/JOJ3
24
5
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

Update JOJ3 Configuration For TAs

manuel 2024-10-26 12:14:21 +08:00
parent 9ad24071f4
commit d0a89afa93
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
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