Evaluate unneeded testcases with low priority
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
This one is connected with #342 and #258. In some contests it's not possible to use #258 due to traditions or some special rules (i.e. all testcases should always be evaluated). But we still can benefit from #258 if #342 is implemented: instead of skipping testcases like in #258 we just lower their priorities in the queue, so this testcases will be evaluated after everything other is done.
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
Start by reading the linked issues #342 and #258 to understand the proposed testcase handling and queue behavior. Trace where testcase priorities are assigned and verify that the completed work evaluates lower-priority testcases after all others while still evaluating every testcase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100