LEdoian
/
recodex-wiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

corrections + todos

Browse Source
master
Teyras 8 years ago
parent db3ab49a23
commit 5c7f91d47e
1 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File

16
Rewritten-docs.md
Unescape Escape View File

@ -639,22 +639,22 @@ that. This is different for each environment (operation system, programming
language, etc.), so each of the environments needs to have separate language, etc.), so each of the environments needs to have separate
configuration. configuration.
Backend understands powerful, but quite low level description of simple Backend works with a powerful, but quite low level description of simple
connected tasks written in YAML syntax. More about the syntax and general task connected tasks written in YAML syntax. More about the syntax and general task
overview can be found on [separate overview can be found on [separate
page](https://github.com/ReCodEx/wiki/wiki/Assignments). One of the planned page](https://github.com/ReCodEx/wiki/wiki/Assignments). One of the planned
features was user friendly configuration editor, but due to tight deadline and features was user friendly configuration editor, but due to tight deadline and
team composition it did not make it to the first release. However, writing team composition it did not make it to the first release. However, writing
configuration in the basic format will be always available and allows you to use configuration in the basic format will be always available and allows users to
the full expressive power of the system. use the full expressive power of the system.
This section walks through creation of job configuration for _hello world_ This section walks through creation of job configuration for _hello world_
exercise. The goal is to compile file _source.c_ and check if it prints string exercise. The goal is to compile file _source.c_ and check if it prints `Hello
`Hello World!` to the standard output. World!` to the standard output.
The problem can be split into several tasks: The problem can be split into several tasks:
- compile _source.c_ into _helloworld_ by `/usr/bin/gcc` - compile _source.c_ into _helloworld_ with `/usr/bin/gcc`
- run _helloworld_ and save standard output into _out.txt_ - run _helloworld_ and save standard output into _out.txt_
- fetch predefined output (suppose it is already uploaded to fileserver) with - fetch predefined output (suppose it is already uploaded to fileserver) with
hash `a0b65939670bc2c010f4d5d6a0b3e4e4590fb92b` to _reference.txt_ hash `a0b65939670bc2c010f4d5d6a0b3e4e4590fb92b` to _reference.txt_
@ -717,6 +717,10 @@ the program cannot be executed without being compiled first. It is important to
mark this task with _execution_ type, so exceeded limits will be reported in mark this task with _execution_ type, so exceeded limits will be reported in
frontend. frontend.
@todo describe overriding of default (per worker) limits and that we cannot
relax them
@todo state clearly that the limits on stdout, stderr and file IO are shared
```{.yml} ```{.yml}
- task-id: "execution_1" - task-id: "execution_1"
test-id: "A" test-id: "A"

Write Preview
Loading…
Cancel
Save