| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
hitting 100% and staying there for several hours
"Did the workunit complete? If so can you post - the workunit name as well as - the stderr log and I will take a look at it. Thanks, armstrdj" |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
World Community Grid Forums
Category: Support Forum: Android Support Forum OET job, 95+ hours, 100%, still shows "running"? https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,37770 |
||
|
|
stokx
Cruncher Joined: May 20, 2010 Post Count: 2 Status: Offline Project Badges:
|
I'm having this problem too, I reinstalled boinc which didn't help. The tasks its stuck on now are: OET1_0000625_xMBGP-F_rig_64648_1 and OET1_0000625_xMBGP-F-rig_64653_1
This is on a moto e phone (android) which has worked fine on other tasks. Ebola is running fine on my windows 8 laptop. |
||
|
|
Col323
Senior Cruncher Joined: Nov 4, 2008 Post Count: 372 Status: Offline Project Badges:
|
I've seen this on my Nexus 7. The biggest example I saw was the runtime added 6 hours while on 100% (going from ~12 hours to ~18).
I just let them ride. For me, they eventually complete and validate. If nothing else, it gets you closer to the next badge. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
World Community Grid Forums Category: Support Forum: Android Support Forum OET job, 95+ hours, 100%, still shows "running"? https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,37770 That was my thread. The job eventually finished, but my wingman never responded. Last I had seen, the job was re-sent to another device and when I went to check again it had disappeared. So I am unaware if it validated or not. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'm having the same problem now on a Samsung Galaxy S 5
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
The staying at 100% for multiple hours is of -Normal- expectation [On Android], though we don't know what it's doing [hot air processing maybe ;>]. At 99.9% the 8th and final checkpoint is done and most jobs conclude in a jiffy, the longest 'seen' sitting at 100% was for 9 hours. I've confirmed if restarting these [taking long at 100%], they resume from 99.9% and do the same long 100% routine again... it's somehow needed. Not like there's nothing being done.
----------------------------------------Never have observed it on Windows/Linux [when randomly looking in on the client health], ... it's not what I spend time looking for, and since the jobs finish and validate, it is not concerning me, don't even know if the 100% time is fully included in the Elapsed/CPU time as reported on the Result Status page. Anyone looked at that? If it is, it's a non-issue, but for testing patience when it occurs. [Edit 1 times, last edit by SekeRob* at Apr 30, 2015 8:16:16 PM] |
||
|
|
|