| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Africa Rainfall Project
Thread: -0 version sent time keeps updating to current time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges: 
|
I received ARP1_ 0017373_ 001_ 1-- on 22 December and returned it on 23 December. However the _0 version was not sent until 24 December, according to Result status. Each time I look at it the sent time updates to the current time. But the return time is shown as almost 7 days after my version was sent.
Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges:
|
Update -0 version stopped updating at 7:52:41 GMT (UTC)
Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges:
|
Sent time has restarted updating.
Mike |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Present screenshots of the 2 differential observations if it still occurs.
----------------------------------------Fortunately, your client will never know, not of the change in sent time or any change in due time, latter which techs occasionally do when there was an long outage, upload problem for instance, to prevent copies being sent out prematurely. FYI, if you hover over the Time Due & Return Time parts in the column header, you see there to be 2 different sort order links. Click on Time Due and you see when all your tasks are due in ascending order. That's what counts. PS, my ARP tasks or any other task have a sent time frozen in the past. ARP1_ 0019518_ 001_ 1-- In Progress 12/23/19 16:21:53 12/30/19 16:21:53 0.00 / 0.00 0.0 / 0.0 ARP1_ 0011131_ 001_ 1-- In Progress 12/23/19 07:41:50 12/30/19 07:41:50 0.00 / 0.00 0.0 / 0.0 ARP1_ 0012271_ 001_ 0-- In Progress 12/22/19 01:54:47 12/29/19 01:54:47 0.00 / 0.00 0.0 / 0.0 ARP1_ 0019523_ 001_ 1-- In Progress 12/22/19 00:23:24 12/29/19 00:23:24 0.00 / 0.00 0.0 / 0.0 [Edit 2 times, last edit by Former Member at Dec 24, 2019 11:35:58 AM] |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges:
|
Full print
Workunit Status Project Name: Africa Rainfall Project Created: 12/22/2019 06:39:04 Name: ARP1_0017373_001 Minimum Quorum: 2 Replication: 2 Result Name OS type OS version App Version Number Status Sent Time Time Due / Return Time CPU Time / Elapsed Time (hours) Claimed/ Granted BOINC Credit ARP1_ 0017373_ 001_ 0-- Microsoft Windows 10 Core x64 Edition, (10.00.18362.00) - In Progress 12/24/19 10:44:12 12/29/19 06:38:28 0.00 0.0 / 0.0 ARP1_ 0017373_ 001_ 1-- Microsoft Windows 7 Professional x64 Edition, Service Pack 1, (06.01.7601.00) 727 Pending Validation 12/22/19 06:39:18 12/23/19 06:35:28 21.55 691.4 / 0.0 Close |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That's what you did not tell, you were looking at the distribution detail screen, not the Result Status page where all is fine. Yes, seeing the same bug there, but it's of no consequence. uplinger will surely fix after x-mas.
|
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Greetings,
In the database, we have sent_time as the 12/24 timestamp. Without digging into millions of lines of scheduler requests and logs to confirm, what is happening is the user was sent that result originally at the 12/22 date (with 7 day deadline). However, the user had an issue on their client (reset or deep freeze refresh) that caused their machine to be registered as the same device. The scheduler tries to resend "lost" work which changes the sent_time to the time they last requested the work unit from us. With the limited number of work units and the excitement around the project, you are noticing this on arp1 tasks, but it actually happens on all tasks. Thanks, -Uplinger |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges:
|
Keith
What I actually found when refreshing was that the sent_time updated several times in fairly quick succession, which doesn't seem to fit with your explanation unless the other party lost and regained the unit several times. Merry Christmas Mike |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges:
|
The other party has still not completed the task but has another 3 days left. However, sent_time is still updating on his record periodically.
Mike |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
Hey Mike,
I can't give too much information out about your wingman, but this is normal behavior for them. This wingman will more than likely get turned into a reliable host only due to the behavior of this specific machine. Thanks, -Uplinger |
||
|
|
|