However, minutes after that I saw a Client Error from 4.30 Beta Test tumbling in that allowed to track down a cause for our major Client Error (a General Access Violation that lists "houghmap.c" in the stackdump) and hopefully fix it. A new Beta will soon be published (no individual speedup, but less client errors).
hmmm I thought the server'd been updated to push the new app out to already queued WUs on the client end. Is there anything in particular I need to kick to get it running on my end?
The WU's in your cache have been assigned to be crunched by the new app even though in BOINC it says they're still assigned to an older app. Only newly assigned work will say 'using app 4.30' under your tasks.
Just to make sure double check in task manager, it should show that the beta app is running.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
4.30's been DLed on all boxes with new work, but they're still running 4.24 for prior WUs (checked via task mangler).
This is entirely normal behaviour. When there is a project generated app change (eg 4.24 -> 4.30) the results will be crunched with the app specified at the time the result was downloaded.
When using the beta app with a current style app_info.xml, it's the intelligence in the app_info.xml which overrides the "branding" of each result and allows any result (no matter how branded) to be crunched with the particular app specified in the app_info.xml file. If you really want any 4.24 "branded" results to be crunched with 4.30 you will need to use the app_info.xml mechanism. If you are even thinking about going to that amount of trouble, you may as well use 4.32 and be done with it :).
The 4.30 has been made
)
The 4.30 has been made "official".
However, minutes after that I saw a Client Error from 4.30 Beta Test tumbling in that allowed to track down a cause for our major Client Error (a General Access Violation that lists "houghmap.c" in the stackdump) and hopefully fix it. A new Beta will soon be published (no individual speedup, but less client errors).
BM
BM
The new Beta App is
)
The new Beta App is there!
Thank you very much for this Beta Test!
BM
BM
hmmm I thought the server'd
)
hmmm I thought the server'd been updated to push the new app out to already queued WUs on the client end. Is there anything in particular I need to kick to get it running on my end?
The WU's in your cache have
)
The WU's in your cache have been assigned to be crunched by the new app even though in BOINC it says they're still assigned to an older app. Only newly assigned work will say 'using app 4.30' under your tasks.
Just to make sure double check in task manager, it should show that the beta app is running.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
Nope, it's not even
)
Nope, it's not even downloaded. Clients are running 5.8.11, .15, and .16. All have been manually updated but none have DLed the 4.30 app.
RE: Nope, it's not even
)
4.30's been DLed on all boxes with new work, but they're still running 4.24 for prior WUs (checked via task mangler).
RE: 4.30's been DLed on all
)
This is entirely normal behaviour. When there is a project generated app change (eg 4.24 -> 4.30) the results will be crunched with the app specified at the time the result was downloaded.
When using the beta app with a current style app_info.xml, it's the intelligence in the app_info.xml which overrides the "branding" of each result and allows any result (no matter how branded) to be crunched with the particular app specified in the app_info.xml file. If you really want any 4.24 "branded" results to be crunched with 4.30 you will need to use the app_info.xml mechanism. If you are even thinking about going to that amount of trouble, you may as well use 4.32 and be done with it :).
Cheers,
Gary.