62 AP_V5 Left In The Field |
![]() |
| log in |
Message boards : Number crunching : 62 AP_V5 Left In The Field
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
| Author | Message |
|---|---|
12! & waiting for purging 8 & 127. I suppose once everything reaches 0 they will start putting the v6 info up there. ____________ SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the BP6/VP6 User Group today! | |
| ID: 1229252 · | |
|
10! | |
| ID: 1229502 · | |
And then there were......8. And then there were......7. ____________ | |
| ID: 1230449 · | |
|
Now 6 | |
| ID: 1230468 · | |
|
We're down to 4! | |
| ID: 1230545 · | |
We're down to 4! make that 3 ____________ | |
| ID: 1231474 · | |
We're down to 4! Is it not around nowish that James Bond steps in to stop the clock ticking. Or Murphy Will it be over for Tuesday | |
| ID: 1231683 · | |
|
Another one has been returned, but now there are 4 Results in progress rather than the expected 2! | |
| ID: 1232407 · | |
Another one has been returned, but now there are 4 Results in progress rather than the expected 2! 'Returned' in that context could just mean yet another deadline passed. That - or any one of a number of other outcomes - will require another resend, and perhaps another 25 days before we can finally put this sequence to bed, if the resend has gone to somebody taking advantage of the newly unlimited caches. | |
| ID: 1232412 · | |
Another one has been returned, but now there are 4 Results in progress rather than the expected 2! Yes, but it came back in 186.88 hours so how can it be a deadline? I guess it could have been aborted. 3 I could understand, but what could cause 4? Two timeout resends? Is there any way to get a list of who has the 4 AP WUs please? | |
| ID: 1232415 · | |
Is there any way to get a list of who has the 4 AP WUs please? Ask Eric to give you sufficient access rights to run a bespoke SQL query against the database? Not going to happen. Test every possible WU ID number? That will (or should) get your IP blacklisted for mounting a DOS attack. Better just to wait. It may be fun watching, but it really doesn't matter, in the overall scheme of things. | |
| ID: 1232417 · | |
Another one has been returned, but now there are 4 Results in progress rather than the expected 2! It ain't me! I had one, but I returned it a couple of weeks ago. I'm also wondering why it went back up to 4. I hope someone in the lab is at least curious enough to check for himself and see if they're out to hosts that are likely to return them. ____________ David Sitting on my butt while others boldly go, Waiting for a message from a small furry creature from Alpha Centauri. | |
| ID: 1232464 · | |
Another one has been returned, but now there are 4 Results in progress rather than the expected 2! Amidst all the power cut problems we seem to have forgotten about this thread. Just noticed AP5 out in the field has now gone up to 5! ____________ | |
| ID: 1233630 · | |
I'm also wondering why it went back up to 4. I hope someone in the lab is at least curious enough to check for himself and see if they're out to hosts that are likely to return them. Simply because tasks that have timed out "return home" to wait for a new host to come along. Until then, they are not out in the field! | |
| ID: 1233768 · | |
I'm also wondering why it went back up to 4. I hope someone in the lab is at least curious enough to check for himself and see if they're out to hosts that are likely to return them. Yes, and with all AP tasks having exactly 25 day deadlines there's likely to be some correlation in timeouts. I don't remember exactly what day they stopped splitting AP v505 tasks, but it was around March 10 and we're getting close to 75 days after that. In pure theory, if one of the first two task replications was completed normally but all the wingmates time out it would be some time in October before the maximum total replications of 10 would be reached. Joe | |
| ID: 1233783 · | |
|
A theoretical 250 days to bounce around peeing everyone off! | |
| ID: 1233901 · | |
I'm also wondering why it went back up to 4. I hope someone in the lab is at least curious enough to check for himself and see if they're out to hosts that are likely to return them. I'm pretty sure a few weeks ago I mathed out that they should all expire by October 1, but I don't remember what my start date was for that math. At any rate, by Halloween, v505 should be dead. ____________ Linux laptop uptime: 1484d 22h 42m Ended due to UPS failure, found 14 hours after the fact | |
| ID: 1233906 · | |
At any rate, by Halloween, v505 should be dead. At haloween the dead do rise from the grave, there are zombies all over the place [around here, anyway] So. There may be a bit of `fun` left in the old bits yet :¬) | |
| ID: 1234457 · | |
|
The SSP is back to showing 4 in the field. It also has 1 waiting for validation. Now I'm wondering if this means the 4 have not had a response from ANY host to which they've been sent. | |
| ID: 1235426 · | |
Message boards : Number crunching : 62 AP_V5 Left In The Field
| Copyright © 2013 University of California |