Detailed results not written to after 60 seconds, exiting!

[Didayolo]

In CodaBench, if the detailed_results.html file is not created, the compute worker stop the execution (without logs on the platform side by the way).

I guess the idea behind this is to be able to have a look at the detailed results during the execution, in real time.

This is cool but not really robust. This causes error because usually this file is created at the end of the execution (especially in old CodaLab bundles).

See:

codabench/docker/compute_worker/compute_worker.py

Line 242 in 232490d

timeout_error_message = f"Detailed results not written to after {expiration_seconds} seconds, exiting!"

Update: if the detailed_results.html file is empty, it creates a bug.

I think the file should be created by Codabench (the compute worker) itself if it does not exist.

[Didayolo]

I have this error again on another challenge:

Detailed results not written to after 60 seconds, exiting!

I think it is important that we fix it, because when the compute worker exit like this, the submission fails with no logs at all. I could retrieve this logs inside the compute worker, but on the side of Codabench interface, the scoring logs just stop.

[Didayolo]

Another take could be simply to remove this expiration of the scoring program.

[LidiaGarrucho]

Using docker pull codalab/competitions-v2-compute-worker:gpu1.1 in the compute worker, I am getting:
Detailed results not written to after 60 seconds, exiting!

Why is this? Thank you!

[Didayolo]

Hi @LidiaGarrucho,

Do you mean that you setup a GPU worker running on the image codalab/competitions-v2-compute-worker:gpu1.1, and then submissions give the errorDetailed results not written to after 60 seconds, exiting! ?

Or are you really implying the error is raised as a response to the docker pull command?

[LidiaGarrucho]

No, I am informing this error didn't dissapear when writing Detailed results running a competition on a compute worker. From this thread seems the scoring timeout was deleted but I am getting this message on the console when writing detailed results, even though the Detailed results are submitted and displayed correctly in HTML format.

[Didayolo]

No, I am informing this error didn't dissapear when writing Detailed results running a competition on a compute worker. From this thread seems the scoring timeout was deleted but I am getting this message on the console when writing detailed results, even though the Detailed results are submitted and displayed correctly in HTML format.

It is actually a warning and not an error. I'll update the message so it is clearer (removing the "exiting" especially). Thank you for the report.