Submissions
The list of every student submission in a course, its filters, the submission panel with tests and source code, and what each verdict means.
Submissions (/teaching/<course>/submissions) lists every graded submission and Excel upload of the students you can see, newest first. All course staff see it; a group admin sees only their own groups’ students’ submissions.
The list
Section titled “The list”Submissions are grouped by day (Today, Yesterday, then dates). A row shows:
- the verdict icon and the student;
- the verdict (for example Accepted, Wrong answer) or the judging state (Waiting, Testing…);
- the problem (an Excel task carries the Excel icon);
- the points (for example “70/100”); for an Excel upload, the points earned;
- the time of submission.
At first the 100 newest entries are shown; Show more adds another 100, up to 500. Find older ones by choosing a student or a problem. New submissions and verdicts appear by themselves.
Students’ practice runs (ungraded) are not listed: only the student sees them.
Filters
Section titled “Filters”| Filter | Selects |
|---|---|
| Group | One group’s or No group students’ submissions (shown when there is more than one choice) |
| Student | One student’s submissions |
| Problem | One problem’s submissions |
| Verdict | Not accepted, one verdict (Accepted, Wrong answer, Compilation error, Runtime error, Time limit exceeded, Memory limit exceeded, Presentation error) or Being checked |
Clear filters shows the full list again. Filters are part of the address, so you can bookmark a filtered list or open it in a new tab.
The submission panel
Section titled “The submission panel”Selecting a programming submission opens its panel on the right (?submission= in the address). An Excel upload opens the task’s results page instead.
staff/teaching/submission-peekThe panel has:
- the submission date and time as its title, then the verdict, the problem, the programming language and the student (on Activity, the course too);
- Message: a conversation with the student about this submission (the submission is attached);
- Tests (passed of total), Slowest (the longest-running test, ms) and Memory (the peak, MB);
- Compiler messages, when there are any;
- Tests: each test’s verdict and time; select a test to see its Input and Expected output, and for samples and every failing test also the program’s output (Your output) and Error output; a Checker message too when the checker left one;
- Similarity: how similar the solution is to other students’ solutions;
- Code with line numbers;
- the links All of this student’s submissions for this problem and This student’s progress.
Course staff see the data of every test, hidden ones included. Once a submission is judged, the student who submitted it sees the same tests and data; other students never see it.
When you can’t see a submission (for example it belongs to a student outside your groups), the panel says “This submission isn’t available. It may belong to a student outside your groups.”
Esc closes the open panel.
Verdicts
Section titled “Verdicts”| Verdict | Meaning |
|---|---|
| Accepted | Every test passed: the problem is solved |
| Wrong answer | The program’s output was wrong in at least one test |
| Compilation error | The program could not be compiled (Python syntax errors included). It doesn’t count towards the daily attempt limit |
| Runtime error | The program crashed while running |
| Time limit exceeded / Memory limit exceeded / Output limit exceeded | The program exceeded the problem’s limit |
| Check failed, System error | Checking failed on our side; the attempt doesn’t count |
| Presentation error, Idleness limit exceeded, Security violation | Only in submissions imported from the old system |
While a submission is being checked, its state shows: Waiting, Compiling, Testing, then Checked. Cancelled means the check was cancelled.
Related pages
Section titled “Related pages”- Home and activity: the submission feed across courses
- Progress and marks
- Similarity