Tried yet another fix on the server end of things. Let me know if you're still seeing maximum time limit elapsed errors.

---

I am still getting maximum time exceeded errors on the n-body work units, though one or a few are now completing successfully. My computer is now going into high priority mode as well. One failed at 82%. Another failed at 85%. It looks like I am getting a mix of successes and failures. These failures were under BOINC x64 version 6.10.60. Since BOINC released a new version, 6.12.26, I have upgraded since then.

I am still getting maximum time exceeded errors on the n-body work units, though one or a few are now completing successfully. My computer is now going into high priority mode as well. One failed at 82%. Another failed at 85%. It looks like I am getting a mix of successes and failures. These failures were under BOINC x64 version 6.10.60. Since BOINC released a new version, 6.12.26, I have upgraded since then.

Is it failing for both the n-body simulation application and the regular one? Or just one of the two?

---

I am still getting maximum time exceeded errors on the n-body work units, though one or a few are now completing successfully. My computer is now going into high priority mode as well. One failed at 82%. Another failed at 85%. It looks like I am getting a mix of successes and failures. These failures were under BOINC x64 version 6.10.60. Since BOINC released a new version, 6.12.26, I have upgraded since then.

Is it failing for both the n-body simulation application and the regular one? Or just one of the two?

With just 4 clicks you to can see Jesse's returned results...

I am still getting maximum time exceeded errors on the n-body work units, though one or a few are now completing successfully. My computer is now going into high priority mode as well. One failed at 82%. Another failed at 85%. It looks like I am getting a mix of successes and failures. These failures were under BOINC x64 version 6.10.60. Since BOINC released a new version, 6.12.26, I have upgraded since then.

Is it failing for both the n-body simulation application and the regular one? Or just one of the two?

With just 4 clicks you to can see Jesse's returned results...

When I clicked they were all correct...

---

I did a few yesterday without problem I think.
However they are very soon out of the database if wingman has them ready as well.
I have only stil two n-body waiting for validation, but mine ran without error.
But that was all before you (Travis) did an update.

---

Greetings from,
TJ

I recently upgraded my BOINC client, and I am still getting some n-body work units that fail due to maximum time limits exceeded. Some n-body work units also pass. Few if any of the regular work units are giving me problems, and the last problem regular work unit I had was with the ATI client failing to record the results to stderr, and that was a week or two ago and has nothing to do with this problem.

I wonder if you might get some help if you visit http://boinc.berkeley.edu/dev/ and use the message boards there or the BOINC projects email lists at http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects for help. There might be a setting that you might be overlooking that could be obvious to another person. The same problem happens to the best of us (e.g. someone failing to declare a variable as volatile in C when using it to spin-wait on an I/O transaction and therefore the compiler optimizes the variable by moving it to a register).

I wonder if you might get some help if you visit http://boinc.berkeley.edu/dev/ and use the message boards there or the BOINC projects email lists at http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects for help. There might be a setting that you might be overlooking that could be obvious to another person. The same problem happens to the best of us (e.g. someone failing to declare a variable as volatile in C when using it to spin-wait on an I/O transaction and therefore the compiler optimizes the variable by moving it to a register).

I've actually been working with Dave Anderson directly on this one. Something weird is going on with our scheduler.

---

I am still getting maximum time exceeded errors on the n-body work units, though one or a few are now completing successfully. My computer is now going into high priority mode as well. One failed at 82%. Another failed at 85%. It looks like I am getting a mix of successes and failures. These failures were under BOINC x64 version 6.10.60. Since BOINC released a new version, 6.12.26, I have upgraded since then.

Is it failing for both the n-body simulation application and the regular one? Or just one of the two?

With just 4 clicks you to can see Jesse's returned results...

When I clicked they were all correct...

LOL...time to increase the time before deletion a little more?

Could it be possible that your settings are not accounting for the possibility that when BOINC responds that there are 12 processors to use that it is failing to account for the hyperthreading my 6-core hyperthreaded processor is presenting? BOINC might be expecting twice the processing power it is actually getting. I noticed that some of the work units that fail on a Core i7 with hyperthreading work well on a Core 2 without hyperthreading.