Have a look at this:

http://setiathome.berkeley.edu/workunit.php?wuid=1160913354

This WU is one of many that I have had error out of me due to Abandonment and has had the smallest time to date.

I'm not sure what the process is for determining time but I do think though that a 15 second window between sent and the reporting deadline is somewhat short and probably signals that something needs to be looked into and/or adjusted.

The minimum probably needs to be a day.

cheers

---

Hi Lionel

There's an "Explain" link at the top of that column which opens a page with the following:

A task's Time reported or deadline field depends on whether the task has been reported yet:

Already reported - The date/time it was reported
Not reported yet, deadline in the future - Deadline, shown in green.
Not reported yet, deadline in the past - Deadline, shown in red.

If the task is already reported then the colour is black.

In the case of this task I believe your machine abandoned the task 15 seconds after it was downloaded. At that point the time was updated to the current time and changed to black. For 14 seconds after it downloaded the time would have been green and a month or more in the future.

Cheers
Jeff

---

It's funny how my errored out tasks rose from circa 50 to circa 500+ over the last 2 days whilst the pipes were maxed out and both of my machines were starving for work.

I have seen WUs come down with ~10 minute deadlines only to be abandoned due to insufficient time to process. There is something not right with the determination of time.

I have sat here and watched it happen.

This will be my last discourse on this issue, I have raised it before but there seems to be a lack of interest in looking into it. After all, it's a waste of bandwidth and activity at both ends. I'll let others point this out in the future as the problem manifests itself and annoys them.

cheers

---

It's funny how my errored out tasks rose from circa 50 to circa 500+ over the last 2 days whilst the pipes were maxed out and both of my machines were starving for work.

I have seen WUs come down with ~10 minute deadlines only to be abandoned due to insufficient time to process. There is something not right with the determination of time.

It's not that they come down with a short deadline. They are initially assigned a normal deadline and then something happens to cause them to be abandoned, and then the deadline gets changed to the current time at that moment. I just don't understand how boinc decides a task is abandoned.

It has been quite common for a task to be assigned to one of your processors but the message not to reach your host; then on the next scheduler contact, the host asks for work for a different processor that can't do the "ghost" task the server previously assigned, so the server would change its deadline to that moment and call it a timeout error.

I wonder, is this the same thing happening and the guys have just changed the way it shows up on the site? I am still seeing some timeout errors, so if this is a terminology change it's not consistent.

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.