Reviewing Submissions

Course maintainers and admins can see every submission each student made on a problem. Students never see each other's work.

The roster

Go to /p/<problem-id>/users — or right-click the problem in the course sidebar and pick users. One row per student who submitted: how many attempts, their latest verdict (pass / partial / fail), and when they were last active.

One student's work

Click a student (or go to /p/<problem-id>/users/<user-id>) for the full picture:

• Every submission in order, with the code and per-test results — output vs expected, runtime, errors
• Headline stats — attempts, last score, runtime, time between first and last attempt, and which attempt first passed everything
• An activity calendar — 30 days of submission activity, colored by best verdict per day; click a day to jump to that day's last run

What to look for

Progression — did they converge on the answer, or repeat the same mistake? The attempt-to-first-pass number tells you who struggled.

Wrong output — their actual return value sits next to the expected one per case; that usually reveals the logic error faster than reading the code.

Errors — crashes show the exception message under the failing case. Common causes: wrong function name, syntax error, unhandled edge case.