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 |
I dont frequent the forums much anymore, but am still a dedicated cruncher
![]() I have an "old" android phone that I have as a dedicated cruncher, it is a Motorola xt912 (droid maxx) running Android 4.4.x. I noticed a few days ago that there was an OET job that was taking abnormally long time. I know there are some jobs that are larger than others, so I thought this may be one of those larger ones. This morning I checked on the progress, and it is listed at 95 hours and change and 100% complete, but it is still listed as "running" with the clock still ticking. Other wus have come and gone on the second core with no problems, and this device has not had any history of hiccups during crunching that I know of. Job name is OET1_0000337_xZAGP_OM_rig_2433_0. Should I just leave it? It has a deadline of 22 Feb. My wingman still hasnt checked in with a completed job either. Hopefully I didnt just burn 4 days of computing time on a dud wu. Thanks in advance for any help. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Has happened to me too on Android and then IIRC, still finished after 9 hours or so
![]() |
||
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Let them run. I have some above 36 hrs on a 1.7 GHz Android too.
----------------------------------------![]() |
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4883 Status: Recently Active Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Let it run. Here is one of mine, 101 hours:
----------------------------------------OET1_ 0000333_ xMBGP-OM_ rig_ 8504_ 1-- android_df0d3b55 Valid 2/11/15 15:58:29 2/17/15 05:07:07 96.15 / 101.54 293.1 / 391.9
4849
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Ok thanks for the quick responses. I'll let it continue and look to see what the final run time is.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just a quick update... the job finally completed at 110 hours and is in PV for now. I'll continue to check and see when my wingman checks in or as I am guessing - "no reply" by the 22nd.
OET1_ 0000337_ xZAGP-OM_ rig_ 2433_ 0-- 719 Pending Validation 2/12/15 05:27:10 2/18/15 07:47:37 110.14 329.9 / 0.0 |
||
|
zxcvbob
Cruncher United States Joined: Jan 12, 2006 Post Count: 35 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
So it goes to 100% and it's really only about halfway done? Or less? Not all jobs loop at the end; maybe half of them do. I'm about to unistall the client and just give up crunching on Android.
|
||
|
|
![]() |