The EverReady WU ... !!!
Anonymous
5 Feb 2005 22:55:30 UTC
Topic 12454
(moderation:
> So, I guess, the new app isn't out yet.
Right. Still testing, validating and debugging the new code...
BM
The EverReady WU ... !!!
)
> Okay, well this workunit is now at 24h50m of cpu time.. guess I just let it
> keep going.. ?
Please take a look at the thread Work Unit not finishing?. I have nothing else to report currently.
BM
BM
> > Like the EverReady
)
> > Like the EverReady Battery's this WU "H1_0368.4__0368.6_0.1_T00_Test02_0"
> on
> > Host "5406" goes on & on & on & on & on & on past the
> 100%
> > Mark. It's been running for over an hour now after showing 100% done.
> >
> > I shut BOINC off in an attempt to get it to finish & all that
> accomplished
> > was to drop both WU's back a 1/2 hour from where they were even though I
> have
> > my Preferences set to Write to disk every 1 second ...
> >
> > Anybody know of a way to pull the Plug on this WU short of reseting the
> > project or do I just have to Crunch on it the rest of my Life ...???
> >
> >
>
> I had one like that PoorBoy, Bruce and the gang wanted me to contiue to run it
> but I deleted it before they asked. It could be part of a group that had a
> problem. anywho I am sure Bruce will see this message...
Yup.
This is the nasty bug in our current app. Fixed in the replacement, which should be ready to distribute very soon (still in testing). You can either let it run to completion. Although it indicates 100% finished, it may take up to another 6 hours to complete. Or just kill it (but lose your credits).
Sorry about this: it's a data driven bug, and one of the reasons that we are still in 'testing' not 'public'.
Bruce
> Basicaly, the Windows
)
> Basicaly, the Windows compiler was optimizing the Benchmark code to run faster!
Actually it detected part of it as a pure waste of CPU cycles while the results being thrown away (well, that's what benchmarks do, isn't it?), thus didn't compile it at all...
BM
BM