I have 3 of the new AP work units fail with this error. All 3 AP work units were issued in this latest batch that started going out after the AP shutdown.

All my previous errors I can account for but I have no idea on these 3 work units.

Nothing changed with my setup!

---

Boinc....Boinc....Boinc....Boinc....

Don´t know if could be related but i get this error: http://setiathome.berkeley.edu/result.php?resultid=3422583824
if you look the the WU produces error aparently when crunched by a CUDA host and no error in normal SETI.http://setiathome.berkeley.edu/workunit.php?wuid=1442833289

---

now up to 5 errors................

---

Boinc....Boinc....Boinc....Boinc....

So....when did you 'Upgrade' to 7.2.42?

Your errors are related to the AP & MB alleged BOINC cleanup error mentioned in two very long threads.

I have 3 of the new AP work units fail with this error. All 3 AP work units were issued in this latest batch that started going out after the AP shutdown.

All my previous errors I can account for but I have no idea on these 3 work units.

Nothing changed with my setup!

Geek@Play, you can't just run any old app on the project, Since you're an Alpha tester, and have access to the Alpha testing threads, you're got to Bench test them first, we have no idea if they work or not, you're running r2163:

http://setiathome.berkeley.edu/result.php?resultid=3423670283

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSSE3 FMA3 SSE4.1 SSE4.2 AVX
AstroPulse v6 Windows x86 rev 2163, V6 match, by Raistmer with support of Lunatics.kwsn.net team. SSE2

r2163 has been withdrawn because it doesn't work correctly:

[quote author=Mike link=topic=1625.msg55087#msg55087 date=1393955754]
Warning

r_2163 for GPU needs to be removed it has the termination issue.
I dont know when you uploaded this rev but it has never been tested.

Claggy

Don´t know if could be related but i get this error: http://setiathome.berkeley.edu/result.php?resultid=3422583824
if you look the the WU produces error aparently when crunched by a CUDA host and no error in normal SETI.http://setiathome.berkeley.edu/workunit.php?wuid=1442833289

Error

Error on call (cudaMemcpy(TripletResults, dev_TripletResults, 2 * grid.x * block.x * grid.y * block.y * sizeof(*dev_TripletResults), cudaMemcpyDeviceToHost)), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_pulsefind.cu, line 318: invalid argument

Has been reported to both Eric and Jason already - we spotted it first with WU 1441160462

Good to see a normal outcome with the standard app in live running - that confirms bench testing carried out offline. The characteristic of these tasks is that they run for a very short time (2 seconds, in the case I watched) and then go into 'temporary exit' and 'waiting to run': and they repeat the cycle again, and again, and again.

The WU names are interesting, too:

07jl13aa.22781.38725.438086664207.12.0, WU true angle range is : 279.183095
23my13ab.29476.393355.438086664207.12.0, WU true angle range is : 252.972605

Seems to be some sort of pattern there.....

(but they're a completely different pattern from Geek's - sorry for hijacking the thread, Geek)

Thanks Claggy,

Some where along the time of the AP outage I must have made some changes. I have reverted to a clean Lunatics 0.41 install. Many work units were re-issued back to me. Looks like I lost some though.

I will run 0.41 for a while and let things work themselves out.

---

Boinc....Boinc....Boinc....Boinc....