WU 03oc03aaxxxx using v4.04 of application is now at 06:08 CPU time with 11% done and has an estimated to completion that is at some 49:55 and still climbing.

My guess is this is one of the bad WU's. Therefore I will abort it.

Next WU is also a 03oc03aaxxxx, I suspect it will do the same.

---

Greetings from Belgium
Thierry
BOINCing since May 2004

WU 03oc03aaxxxx using v4.04 of application is now at 06:08 CPU time with 11% done and has an estimated to completion that is at some 49:55 and still climbing.

My guess is this is one of the bad WU's. Therefore I will abort it.

Next WU is also a 03oc03aaxxxx, I suspect it will do the same.

Yip, I have just got back from hols, I read the news about "bad" WUs. I also have a crazy amount of time to run on the new WUs I downloaded today.

Almost as thought no change over the week I have been away. 3 hours crunching and only 2% done.

---

3 hours crunching and only 2% done

That's not so bad. Looks like a normal WU to me. I'm over 10 hours crunching and at 16%. These are the interesting WUs. :)

---

Well I don't have any machines using tons of memory or workunits stretching into the centuries as the frontpage suggest but a few of my machines will not complete their workunits in time. The p3-600e is showing it done on 8/22 when it is due on 8/4. Heck, even my athlon 1000 is gonna miss it's deadline by a few days. Is there something going on here? Do I have bad workunits? Previously all my machines could finish the workunits in time. I am running 4.19 also...

Same here.

Estimated time 40+ hrs.

I'm guessing this is no bad WU because it is not running in the centuries as stated on the homepage.

But I'm been getting more long WU's
Had one completed in 15 hr (normal WU time is less than 2 hours).

Is this normal?

---

nothing. forget it

---

Luckiest in the world. WMD = Weapon of Mass Distraction

Using TMR's opt app, I completed 2 of the 4.04 WU's in 12-14 hours. Now using standard 4.04 app, one WU is at 8.2% after 3.5 hours, with est. complete ~42 hours. Definately some interesting WU's, not the bad, large ones on the front page, already had a couple of those.

---

If you get a real bad WU, your progress stays 0%, and the seti client consumes more and more memory before math, gets into swap, causing frequent disk access. So you'll notice it's evidently a bad WU. I hope now you will not get bad WUs. Eric fixed it in a few hours and cancelled all the bad WUs.

So you shouldn't abort the WU if it progresses above 0%.

And usually, it is slow until 50%-60%, but after that, the cruncher speeds up.

---

Luckiest in the world. WMD = Weapon of Mass Distraction

I just canceled one that has been at 0 for an unknown time (greater than an hour on a 2 GHz PC).

---

BOINC WIKI

If you get a real bad WU, your progress stays 0%, and the seti client consumes more and more memory before math, gets into swap, causing frequent disk access. So you'll notice it's evidently a bad WU. I hope now you will not get bad WUs. Eric fixed it in a few hours and cancelled all the bad WUs.

So you shouldn't abort the WU if it progresses above 0%.

And usually, it is slow until 50%-60%, but after that, the cruncher speeds up.

Hello Tetsuji,

thanks for the clear answer on the question when a bad WU shows up. This makes it more clear.

---

Greetings from Belgium
Thierry
BOINCing since May 2004

When I came into work today I notice that my LONG running WU had aborted.

7/28/2005 9:55:43 PM|SETI@home Beta Test|Resuming result 03oc03aa.9124.208.178408.43_1 using setiathome_enhanced version 4.04

7/28/2005 10:23:02 PM|SETI@home Beta Test|Aborting result 03oc03aa.9124.208.178408.43_1: exceeded CPU time limit 108750.000000
7/28/2005 10:23:02 PM|SETI@home Beta Test|Unrecoverable error for result 03oc03aa.9124.208.178408.43_1 (Maximum CPU time exceeded)
7/28/2005 10:23:02 PM|SETI@home Beta Test|Deferring communication with project for 1 minutes and 0 seconds
7/28/2005 10:23:03 PM||request_reschedule_cpus: process exited
7/28/2005 10:23:03 PM|SETI@home Beta Test|Computation for result 03oc03aa.9124.208.178408.43_1 finished
7/28/2005 10:23:04 PM|SETI@home Beta Test|Started upload of 03oc03aa.9124.208.178408.43_1_0
7/28/2005 10:23:06 PM|SETI@home Beta Test|Finished upload of 03oc03aa.9124.208.178408.43_1_0
7/28/2005 10:23:06 PM|SETI@home Beta Test|Throughput 308000 bytes/sec

So, by reading the other post, I thought 4.04 would not have a problem?

I have another that was picked up at the same time and was wondering if that would have the same problem?

(I know this is a test!!!! - Notice no comments about credit :) )

---

So, by reading the other post, I thought 4.04 would not have a problem?
I have another that was picked up at the same time and was wondering if that would have the same problem?

The error that caused your long WU to abort, Maximum CPU time exceeded, was supposed to have been corrected by Eric. (The problem was in the WU, not with the 4.04 application.) However, some people are still reporting problems with work aborting with this error. It's anybody's guess if it will continue to be a problem with your next WU. I'd certainly say it's still worth crunching!

---

I will then keep on crunching my current work unit. Thanks!

---