testmycode / testmycode/tmc-server
Gather statistics about submission processing times
Open
Nobody has claimed this yet.
easy
enhancement
lowprio
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
Description
Each submission should record when its run was completed. completed_at - updated_at is then the actual running time, including the time waiting for a free processor. This helps estimate the running times for each exercise, monitor resource usage and even detect breakage.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating where submissions are persisted and where processing finishes; done means each submission records its completion time and the stored timestamps support measuring total processing time, including processor wait time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- analytics, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100