Skip to content

Runs should (must at WFs) get published as soon as available #244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
eldering wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Runs should (must at WFs) get published as soon as available #244

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions Contest_API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1839,6 +1839,9 @@ Properties of run objects:
| contest\_time | RELTIME | Contest relative time when run completed.
| run\_time | number | Run time in seconds. Should be a non-negative integer multiple of `0.001`. The reason for this is to not have rounding ambiguities while still using the natural unit of seconds.

A CCS should create each run object as soon as it is ready.
This will for example allow clients to track judging progress in real-time.

#### Examples

Request:
Expand Down
5 changes: 5 additions & 0 deletions Contest_Control_System_Requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -990,6 +990,11 @@ return from the `/access` endpoint:
}
```

Furthermore, the CCS must satisfy the following:

- It must publish [run](contest_api#runs) objects in real-time, so
that ICPC-Live can track and publish judging progress.


#### Access Restrictions

Expand Down