Folding Forum

Hello. I noticed that none of the WUs that my client has dumped have been marked as such on apps.foldingathome.org/wu, nor have they been reassigned.

For example: Project 18498 (Run 61, Clone 31, Gen 72)
This was dumped due to an error, on 2025-05-19 at 15:54:39: We can see that the results were posted successfully. But if we look at https://apps.foldingathome.org/wu#proje ... =31&gen=72, we do not see a "Dumped" result, and even two days later, nobody else has completed the WU. Which is certainly possible for benign reasons (assigned to a machine that was then powered off), but highly unlikely, since this exact pattern has also occurred with three other WUs; dumped some time ago with HTTP_OK, and still not completed by anyone:

• Project: 18251 (Run 88, Clone 0, Gen 217), reported dumped to highland3.seas.upenn.edu at 2025-05-19 19:00
• Project: 17650 (Run 110, Clone 0, Gen 451), reported dumped to pllwskifah2.mskcc.org at 2025-05-19 19:04
• Project: 18238 (Run 681, Clone 3, Gen 49), reported dumped to highland1.seas.upenn.edu at 2025-05-20 05:14

I don't think this is the intended behaviour, because the client explicitly tells the server that the WU is abandoned, but it looks like the project is still waiting for it to time out. I'll check back and see when these actually get reassigned and completed.

Thanks, developer has been notified

Since you are using v8 client, Dumped WUs are all logged to Run 0, Clone 0, Run 0 due to a long time server bug.

toTOW wrote: ↑Sat Feb 22, 2025 10:50 pm Since you are using v8 client, Dumped WUs are all logged to Run 0, Clone 0, Run 0 due to a long time server bug.

Code: Select all

Frogging101 	86978 	9B459077E75C582C 	0 	2025-02-19 15:51:29 	2025-02-19 15:54:39 	2025-02-19 16:00:15 	0,002 	Dumped

Interesting. It only happens with the V8 client, you say?

Now, someone else has completed that WU, and we can see that it took two days for it to be reassigned: https://apps.foldingathome.org/wu#proje ... =31&gen=72

Which means the server waited until the timeout. That's quite a waste of time.

Frogging101 wrote: ↑Sun Feb 23, 2025 5:48 am Interesting. It only happens with the V8 client, you say?

That's what the dev said when I reported the issue a long time ago.

Frogging101 wrote: ↑Sun Feb 23, 2025 5:48 am Which means the server waited until the timeout. That's quite a waste of time.

Either it waited until the timeout, or the the demand for this kind of work is not high and it took some time until someone asked for work for similar hardware ...