Peculiar progress status, 500 days to completion, but validates o.k.

Message boards : Number crunching : Peculiar progress status, 500 days to completion, but validates o.k.
Message board moderation

To post messages, you must log in.

AuthorMessage
Gene Project Donor

Send message
Joined: 26 Apr 99
Posts: 150
Credit: 48,393,279
RAC: 118
United States
Message 1960738 - Posted: 18 Oct 2018, 6:42:00 UTC

I have noticed some peculiar progress status readings on certain work units (CPU SSE41 app) from the
15oc18ac.26994.213998.9.36.xxxx work unit set, specifically the ..175_0 / ..187_1 / ..194_1 / ..242_0 tasks. They run to completion o.k. and seem to be validating o.k. as wingmen report in. But here's what is really odd: Progress sticks at 0.004% for 26:22 (minutes:seconds) elapsed time while time remaining also is stuck at the same 26:22 value; then suddenly time remaining jumps to 460 DAYS and increments upward with each elapsed second while the progress remains stuck at 0.004%. Some minutes later (at 28:56 for one example case) the progress suddenly jumps to 82.768% and time remaining falls to (a more reasonable) 05:59. Progress remains frozen at 82.768% for another 2 or 3 minutes then jumps to 92.159%. Another 30 seconds or so and progress jumps to 97.336% - then another 15 seconds or so and task goes to normal 100% completion with elapsed time of 32:10 or so. All the four cases I saw today had estimated run times of 26:22 and the weird jump in time remaining occurred at exactly that elapsed time.
(I have boinc 7.6.33, Linux, app is MBv8_8.22r3711_sse41.)
I think I saw something like this a few months ago. I was, then, on the point of aborting a task that showed no progress, and hundreds of days remaining but while I was inspecting the situation, and considering how long to wait before terminating the task, it "recovered" and finished in much the same manner as described above.
It doesn't seem to be a critical issue. Maybe boincmgr is confused by some parameters the application reports for rare instances of work units. Just thought I would mention it in case others see something similar.
ID: 1960738 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1960744 - Posted: 18 Oct 2018, 8:11:39 UTC - in response to Message 1960738.  

Yes, we have been dealing with those tasks and similar ones for a couple of months now. Nobody has mentioned it other than in passing and I don't think anyone knows why they have this behavior. Best to just ignore them with respect to stuck progress bar and timers and just let them finish up. They finish up in the normal time for their particular species of task anyway. You will also see them in high priority mode because of the illogical time remaining timer. Wonder if anyone will jump in and explain this behavior.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1960744 · Report as offensive

Message boards : Number crunching : Peculiar progress status, 500 days to completion, but validates o.k.


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.