That's totally normal.
Most of the tasks you crunch will have to be crunched by another participant to verify that you both return good results. The more tasks that you successfully return the higher confidence the servers will have so that more and more of your task will not need a verification.
The deadlines for tasks are normally 1 or 2 weeks depending on the type of task. If your wingman misses the deadline then the task get sent to someone else with a new 1 or 2 week deadline, so the time a task is pending validation can be several weeks if it needs to be sent out multiple times before someone actually completes it.
For Gravity wave tasks there can also be a delay before the tasks is sent to another participant as the server will wait for someone with the right set of data files to process the tasks, eventually the server will stop waiting and send the tasks regardless. I've seen the number 336 hours in the logs and if that's the upper limit then the server might wait up to 14 days to try and find a host with the right set of data files.
I still have tasks from mid-late May that aren't being validated, although their complete. Any reason why? Will they eventually be validated?
If you click on a task you will see this:
Minimum quorum:2
Initial replication:2
Max # of error/total/success tasks:20, 20, 20
That means it is inititally sent to 2 people, then if someone aborts it, doesn't return it in time etc it can be sent out up to 20 MORE times before the units is marked as bad and the Project handles it. In short there is nothing wrong you are just waiting on your wingman as Holmis said.
That's totally normal. Most
)
That's totally normal.
Most of the tasks you crunch will have to be crunched by another participant to verify that you both return good results. The more tasks that you successfully return the higher confidence the servers will have so that more and more of your task will not need a verification.
The deadlines for tasks are normally 1 or 2 weeks depending on the type of task. If your wingman misses the deadline then the task get sent to someone else with a new 1 or 2 week deadline, so the time a task is pending validation can be several weeks if it needs to be sent out multiple times before someone actually completes it.
For Gravity wave tasks there can also be a delay before the tasks is sent to another participant as the server will wait for someone with the right set of data files to process the tasks, eventually the server will stop waiting and send the tasks regardless. I've seen the number 336 hours in the logs and if that's the upper limit then the server might wait up to 14 days to try and find a host with the right set of data files.
brit wrote:I still have
)
If you click on a task you will see this:
Minimum quorum:2
Initial replication:2
Max # of error/total/success tasks:20, 20, 20
That means it is inititally sent to 2 people, then if someone aborts it, doesn't return it in time etc it can be sent out up to 20 MORE times before the units is marked as bad and the Project handles it. In short there is nothing wrong you are just waiting on your wingman as Holmis said.