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:
Code: Select all
15:51:32:I1:WU2:Project: 18498 (Run 61, Clone 31, Gen 72)
15:54:39:I3:WU2:Dumping gVEQtG3hqy4mAlkRB1pMeOHzOA385aEj6vae7JyKLTU
15:54:39:I1:WU2:Sending dump report
15:54:39:I1:OUT14:> POST https://vav21.fah.temple.edu/api/results HTTP/1.1
15:54:39:I1:OUT14:< HTTP/1.1 200 HTTP_OK
15:54:39:I1:WU2:Dumped
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.