codalab / codabench

Codabench is a flexible, easy-to-use and reproducible benchmarking platform. Check our paper at Patterns Cell Press https://hubs.li/Q01fwRWB0
Apache License 2.0
77 stars 28 forks source link

Failure status: strange behaviour #1342

Closed daviddanan closed 6 months ago

daviddanan commented 9 months ago

Hi, i am one of the organizer of the following competition https://www.codabench.org/competitions/1534/

A competition participant reported a strange behaviour regarding the status. His submission went through the whole pipeline (ingestion program, scoring program), he even obtained a score but the status indicates "Failed". I don't understand why, it does not make sense to me, and there is no visible issue within the logs. Could you do something about it?

Thanks.

Didayolo commented 9 months ago

Hi, do you know the ID of the submission and the username of the submitter? Did it happen to other submissions?

daviddanan commented 9 months ago

Hi. Yes, it happenned for several submissions. Here is the complete list of submissions that failed like that so far:

username: 404error Ids that failed: 47879, 47703, 47702, 47594, 47592, 47591, 45824,

username: binhnk Ids: 45161,44932

Didayolo commented 9 months ago

For record: I am re-running submission 47879 (now with ID 48322).

Didayolo commented 9 months ago

Update: the re-run did not fail. I have currently no explanation on the "Failed" status on the first run.

We will try to investigate this problem. In the meantime, you can indicate your participants to submit again if an error occur.

daviddanan commented 9 months ago

This is quite strange because when i have a look at the submission it did fail as showed below. Even worse, there is no score, now.

failedSubmission

According to the submitter, it fails afterward which seems to be consistent with your test. Any idea?

Didayolo commented 9 months ago

Oh sorry, you are right. I made a confusion between "48322" and "48332"

Capture d’écran 2024-02-27 à 17 42 20 Capture d’écran 2024-02-27 à 17 42 01

As you are using your own queue, I can't connect to the worker to find any interesting logs here.

I suggest that you:

Didayolo commented 6 months ago

I close this issue because it is very specific. Feel free to re-open it if needed.