codalab / codalab/codabench

Task 2 repeatedly fails on ingestion_hostname-worker2 with no logs

Open
#2,465 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Competition-specific User-specific
Dominant language
Python
Stars
176
Forks
74
Avg merge
5d 3h
Merged PRs (30d)
21

Description

Dear Codabench Support Team,
The AV-Deepfake1M Task 2 evaluation repeatedly fails on Codabench
without providing any logs.

  Competition: https://www.codabench.org/competitions/4221/
  Submission IDs:
      853339: Task 1 succeeded, but Task 2 produced no result or logs
      853566: Task-2-only submission failed with no logs
      853589: Task-2-only submission failed again with no logs
  
  The latest submission shows:
  ingestion_hostname-worker2
  
  Codabench reports:
  "Child task failed or non-zero return code"
  but the detailed results page says:
  "No logs available for this submission."
  
  The archive integrity and required root-level filenames have been verified.
  Could you please inspect/restart the Task 2 ingestion worker and rerun one
  of the failed submissions?
  
  This appears consistent with Codabench's known compute-worker issue:
  https://github.com/codalab/codabench/issues/1205
  
  Best regards
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Task 2 ingestion worker behavior for submission IDs 853339, 853566, and 853589, then read the related compute-worker issue #1205. Reproduce the failure on ingestion_hostname-worker2 and inspect why the child task returns a non-zero code without logs. Done means a rerun completes or exposes usable logs and results.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.