One validate error; ps_test_4_121257.

ps_test_4_111483_0

Ran with no visible problems.

64-bit Windows Vista SP2
BOINC 6.10.58
GTS 450 graphics board

Validated OK also.


An idea on how to reduce the server load: Add a wrapper that can run the current application perhaps 10 times with separate input files each time, then compress all the output files into a single file. Would need the validator changed to give it the capability of giving credit for only part of these runs, though.

The ps_test_4_X I have seen where completed and validated.

Running on BOINC 6.10.58

---

Greetings from,
TJ

28.05.2011 14:06:22 Milkyway@home Computation for task ps_test_4_141327_0 finished
successfully

Boinc 6.10.60
AMD Catalyst 11.3 (ATI HD 4850)
Windows 7 (64 bit)

5/28/2011 1:19:42 PM | Milkyway@home | Starting task ps_test_4_223018_1 using milkyway version 62
5/28/2011 1:20:33 PM | Milkyway@home | Starting task ps_test_4_213246_2 using milkyway version 62
5/28/2011 1:21:16 PM | Milkyway@home | Starting task ps_test_4_208505_1 using milkyway version 62

5/28/2011 1:21:15 PM | Milkyway@home | Aborting task ps_test_4_223018_1: exceeded elapsed time limit 92.16 (3958564.39G/42951.85G)
5/28/2011 1:22:06 PM | Milkyway@home | Aborting task ps_test_4_213246_2: exceeded elapsed time limit 92.16 (3958564.39G/42951.85G)
5/28/2011 1:22:50 PM | Milkyway@home | Aborting task ps_test_4_208505_1: exceeded elapsed time limit 92.16 (3958564.39G/42951.85G)

An idea to check: Are all of the workunits still exceeding the time limit running under 6.12.* versions of BOINC? I've seen some posts on the Boinc_dev site saying that many of those versions have problems calculating time limits correctly. I still use version 6.10.58, since I've not yet seen anything on new features in the 6.12.* series that I have any use for.

An idea to check: Are all of the workunits still exceeding the time limit running under 6.12.* versions of BOINC? I've seen some posts on the Boinc_dev site saying that many of those versions have problems calculating time limits correctly. I still use version 6.10.58, since I've not yet seen anything on new features in the 6.12.* series that I have any use for.

I have noticed a problem with 6.12.26 also. As an example, 4 task should be at 03:10 but 3 are at 03:10 and one at 00:31, then it all resets to a very long remaining time after the 00:31 task runs. Switching back to 6.10.58.

some test WU computed successfully on XP SP3 & 3850 Cat 11.3

---

DSKAG Austria Research Team: http://www.research.dskag.at

The ps_test_4 unit I got seems to be running fine...OC'd GTX 460 on a Pentium 4 system, WinXP32 and BOINC 6.10.58.

---

they all work fine
boinc 6.12.26 (x64)
win7 of nine x64
HD5850
HD6950

I#ve got a number of this ps_test_4... tasks. They all work fine and produce results.

I7-Processor with Win7 X64
Boinc 6.10.58 (x64) and since yesterday 6.12.26 (X64)

12/06/2011 17:38:53 Milkyway@home Aborting task ps_test_4_864419_0: exceeded elapsed time limit 359.170451
12/06/2011 17:38:54 Milkyway@home Computation for task ps_test_4_864419_0 finished

Running on HD3850 and BOINC 6.10.18.



EDIT: and the next one...

12/06/2011 18:13:20 Milkyway@home Aborting task ps_test_4_864457_1: exceeded elapsed time limit 368.588994
12/06/2011 18:13:21 Milkyway@home Computation for task ps_test_4_864457_1 finished

Separation tasks run btw OK on this machine.

---

OK, now the server side DCF kicked in and solved the problem. Now the ps_test WUs have estimated run time little longer than the 213Cr separation WUs, so that should be OK... I hope.

---

First time I've had errors on test WUs.

6/13/2011 5:18:21 PM Milkyway@home Starting ps_test_4_947202_0
6/13/2011 5:18:21 PM Milkyway@home Starting task ps_test_4_947202_0 using milkyway version 82
6/13/2011 5:18:22 PM Milkyway@home Aborting task ps_test_4_945949_0: exceeded elapsed time limit 82.951068
6/13/2011 5:18:53 PM Milkyway@home Computation for task ps_test_4_945949_0 finished
6/13/2011 5:18:53 PM Milkyway@home Starting ps_test_4_947184_0
6/13/2011 5:18:53 PM Milkyway@home Starting task ps_test_4_947184_0 using milkyway version 82
6/13/2011 5:19:42 PM Milkyway@home Aborting task ps_test_4_947202_0: exceeded elapsed time limit 79.493290
6/13/2011 5:20:02 PM Milkyway@home Computation for task ps_test_4_947202_0 finished
6/13/2011 5:20:14 PM Milkyway@home Aborting task ps_test_4_947184_0: exceeded elapsed time limit 79.493290
6/13/2011 5:20:44 PM Milkyway@home Computation for task ps_test_4_947184_0 finished

---

Same here...

6/13/2011 11:05:49 PM Milkyway@home Starting task ps_test_4_964533_0 using milkyway version 82
6/13/2011 11:08:40 PM Milkyway@home Aborting task ps_test_4_964533_0: exceeded elapsed time limit 169.776411
6/13/2011 11:09:40 PM Milkyway@home Computation for task ps_test_4_964533_0 finished
6/13/2011 11:09:43 PM Milkyway@home Sending scheduler request: To report completed tasks.
6/13/2011 11:09:43 PM Milkyway@home Reporting 1 completed tasks, not requesting new tasks
6/13/2011 11:09:44 PM Milkyway@home Scheduler request completed

That's what came in my messages...

BTW...My system specs:

Win 7 64-bit
8GB RAM
ATI Radeon HD4850 Series GPU
Catalyst 11.5
ALL drivers up to date

Paul

---

Same here...

Same here...

Could those still seeing this problem mention which version of BOINC they are using?

I've seen a few messages that suggest that some of the 6.12.* versions have problems calculating how long the workunits should be allowed to run, and producing the correct answer.

I'm still using 64-bit Windows Vista BOINC 6.10.58, and not seeing this problem.

Looks good now... (64-bit Win 7 BOINC 6.10.58

6/14/2011 12:38:11 AM Milkyway@home Starting task ps_test_4_965975_1 using milkyway version 82
6/14/2011 12:39:54 AM Milkyway@home Computation for task ps_test_4_965975_1 finished

6/14/2011 12:42:27 AM Milkyway@home Starting ps_test_4_968681_0
6/14/2011 12:44:06 AM Milkyway@home Computation for task ps_test_4_968681_0 finished

6/14/2011 12:43:46 AM Milkyway@home Starting ps_test_4_967598_1
6/14/2011 12:45:29 AM Milkyway@home Computation for task ps_test_4_967598_1 finished

---

Since my first reporting of a failed test unit, I've only had one other one.

6/14/2011 4:55:53 AM Milkyway@home Starting task ps_test_4_982172_1 using milkyway version 82
6/14/2011 4:58:32 AM Milkyway@home Aborting task ps_test_4_982172_1: exceeded elapsed time limit 157.564068
6/14/2011 4:59:32 AM Milkyway@home Computation for task ps_test_4_982172_1 finished
6/14/2011 4:59:35 AM Milkyway@home Sending scheduler request: To report completed tasks.
6/14/2011 4:59:35 AM Milkyway@home Reporting 1 completed tasks, not requesting new tasks
6/14/2011 4:59:36 AM Milkyway@home Scheduler request completed

All the same info in my messgaes - exceeded elapsed time limit.

I apologize for not mentioning the BOINC version. I guess the sand I was driving in was a little softer than what I thought...lol.

My specs:

Win7 64-bit
8GB RAM
ATI Radeon HD4850 w/2GB
CCC 11.5
BOINC 6.10.60
ALL Drivers current

I've only seen 2 out of the many I've ran since then. My GPU seems to be the one that has the trouble, as the CPU is doing great. I'm not going to complain much if only 2 out of 20 have exceeded time limits.

Paul

---

Since my first reporting of a failed test unit, I've only had one other one.

Seems there was a run of the test WUs that were all bad. They're also working OK here now. Most wouldn't even notice them as the database is purged too quickly.