Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 693 times and has 1 reply Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
confused Broken CMD2 app version 613?

Hi,

my client got some WUs for CMD2 around June 1st. One of this WU (CMD2_0001-PP1BA.clustersOccur-TPM3A.clustersOccur_188) took 64 hours while "normal" WUs take only 3-5 hours. Another client rendered 244 hours - more than 10 DAYS! We both got app version 613 and our claimed points were not granted.
2 of my other WUs for CMD2 are still in validation...

This was reason for me to stop all work for CMD2 some days ago! There app version has to be fixed I think...
Something known about these errors?

Christoph
[Jun 13, 2009 9:34:40 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Steve WCG
Senior Cruncher
Joined: May 4, 2009
Post Count: 216
Status: Offline
Reply to this Post  Reply with Quote 
Re: Broken CMD2 app version 613?

A new version has been developed, tested and released to production 6.14 ... you should no longer see monster WUs.
[Jun 13, 2009 12:18:59 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread