| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Has the fahv app version 7.32 and shorter tasks caused a u-turn? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Incredibly, whilst away and simap blipping work supply, fahv jobs have been trickling through passed. New device record of 15 sequential without ending in signal 11 or getting a 193. More amazing, 10 are valid, just 2 copies and several of the very last have been allowed to do it alone such as this last one
Project Name: FightAIDS@Home - Vina Created: 09/17/2014 13:01:28 Name: FAHV_x2O4S-B-AS_0880290_0514 Minimum Quorum: 1 Replication: 1 FAHV_ x2O4S-B-AS_ 0880290_ 0514_ 0-- 732 Valid 9/27/14 02:30:49 9/27/14 08:34:31 5.59 58.1 / 58.1 Reliable all of a sudden, shorttracked  Maybe just maybe the u-turn was taken, though with the android stats of just 144k credit for yesterday, the volunteers may still be struggling to 'want to' get back or still struggling on the long monsters. Anyways, last 15 were all 'shorties' that ran from 4 to 6.5 hours. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Of course, no wood in sight and number 16 went kaboom, reliability gone, wcg always testing how to destroy reputations.
FAHV_ x2O4S-A-AS_ 0880255_ 0259_ 4-- - In Progress 9/27/14 15:28:24 10/1/14 03:28:24 0.00 0.0 / 0.0 FAHV_ x2O4S-A-AS_ 0880255_ 0259_ 3-- 732 Error 9/27/14 13:19:09 9/27/14 15:28:13 1.74 18.0 / 0.0 FAHV_ x2O4S-A-AS_ 0880255_ 0259_ 2-- 732 Error 9/26/14 08:13:16 9/27/14 13:14:48 3.82 49.6 / 0.0 FAHV_ x2O4S-A-AS_ 0880255_ 0259_ 1-- 732 Error 9/25/14 21:55:54 9/26/14 08:12:44 5.36 37.1 / 0.0 FAHV_ x2O4S-A-AS_ 0880255_ 0259_ 0-- - In Progress 9/25/14 21:54:40 10/5/14 21:54:40 0.00 0.0 / 0.0 The odd thing is, the really odd thing is, in many cases with fahv on android it's a repair task that is responsible. Here 2 signal 11 and a 193 sigsegv. Why is that? Of course now all the do-it-alone results are turning pending verification and an extra copy is being send out post factum. FAHV_ x2PQZ-A-AS_ 0880301_ 0628_ 1-- - In Progress 9/27/14 16:21:25 10/1/14 04:21:25 0.00 0.0 / 0.0 FAHV_ x2PQZ-A-AS_ 0880301_ 0628_ 0-- 732 Pending Verification 9/27/14 11:02:16 9/27/14 16:19:25 4.41 45.7 / 0.0 Now when pretty please will we get a do-not-send-repairs option on the device profiles, and let the owners of the project run these bad tasks on their private cluster? Would that not be a good way to go? |
||
|
|
armstrdj
Former World Community Grid Tech Joined: Oct 21, 2004 Post Count: 695 Status: Offline Project Badges: 
|
There is definitely a correlation to shorting running tasks having a lower error rate as you have observed. Unfotrunately we are still working to get the last of the long running workunits through the system. We will continue to work on the Android issues but users should start seeing better outcomes once the workunit sizes settle back down.
Thanks, armstrdj |
||
|
|
|