Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 52
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
And another machine (not used very much) had a HCC WU in progress which was several days overdue. I aborted that WU and expected that the cached CMD2 unit (still old version) would fail immediately. But that did not happen. The CMD2 WU started fine and is now running some hours. To add to the strange behaviors after the signature update, this CMD2 WU resulted also in an error: Result Name: CMD2_ 1550-2QZU_ A.clustersOccur-2J8H_ A.clustersOccur_ 10_ 0-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> Input file wcg_hcmd2_maxdo_6.15_windows_intelx86 missing or invalid: -120 </message> ]]> Strange here: The WU was started at about 08:00 with no other WU in cache. The result was reported at 18:44 with 0:00 runtime, with a download of a new WU at the same time. So I lost another ~10h runtime. Greetings Thorsten |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
On Windows I've forced mixes of old and new for same science to run concurrently, nothing I do allows me to force this off, so it's a riddle the techs will have to analyse. Until then nothing much can be done. --//-- edit: strike that. [Edit 1 times, last edit by Former Member at Mar 3, 2011 11:17:03 AM] |
||
|
|
![]() |