Failed submission marked as Finished
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 56/100
Research direction
Use the provided bundle and failing submission to reproduce the issue in a multi-task competition. Trace how child submission failures determine the parent submission's status, then run the relevant tests for submission processing. Done when the parent is marked as failed rather than "Finished" when both child submissions fail.
Written by the indexing model from the issue text.
Description
In a multi-task competiiton when I upload a submission which is supposed to fail, I see that both child submissions fail but the parent is marked as "Finished"
To reproduce this problem use this bundle: Submission_Delete_Bundle.zip and this submission: Submission_Delete_Failing_Submission.zip
- Dominant language
- Python
- Stars
- 181
- Forks
- 80
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 30
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from codalab/codabench
-
Wrong count for failed submissions in Resource interfacePossibly taken @ihsaan-ullah claimed this today. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Beginner Enhancement UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
All issues in codalab/codabench
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
SR_SECURITY_DESCRIPTOR.fromString drops the SACL when no DACL is presentPossibly taken @paul7436 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
equinor/fmu-sumo-uploader#302 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelscope/evalscope#1821 ·
Maintainers usually reply within 1 day
-
Sanity on ansible-core devel fails: ignore-2.23.txt references the removed import-3.9 testPossibly taken @yurnov claimed this today. Openneeds_triage
Difficulty 1/5 Under an hour Newbie friendliness 91/100
ansible-collections/kubernetes.core#1275 ·
Maintainers usually reply within 1 day