> I have an endless loop in "H1_0059.9__0060.0_0.1_T05_Test02" after 100% + a
> memory leak at now 88MB to be increasing. Pls check it out!
>
> Boinc 4.16 using...Einstein v4.72
>
Same here for result H1_0073.4__0073.8_0.1_T02_Test02_4
using einstein version 4.72, Boinc 4.16.
I'm having the same problem with H1_0073.4__0073.8_0.1_T04_Test02_3
The even bigger problem is that it is running alongside seti@home and predictor. When the work unit gets suspended, it shows 8.5 hours of CPU time. Next time the einstein project comes up, the CPU time drops down to 7.something hours which would seem to indicate that the progress isn't being recorded while the infinite loop is in progress so the unit would likely never reach the maximum FLOPS.
> Honza:
>
> > Same here for result H1_0073.4__0073.8_0.1_T02_Test02_4
> > using einstein version 4.72, Boinc 4.16.
>
> Hm, seems that this result has been finished correctly... did you terminate it
> or was it just taking a long time in 100%?
>
> BM
Sorry for not reporting final outcome. I suspended this particular WU by BOINC Manager so Einstein took another one. Finally, i let it run overnight and according to BOINCView - it took another extra hour of computing time and uploaded.
Actually the current WUs crunch in three steps: Two doing the analysis of the detector data (shown as 0-50% and 50.01-100%) and then we do a step that does a comparison of some sort. The last step we thought should not take enough time to give it a full % of the progress, but apparently there are cases in which it takes quite longer than we expected.
In addition to that there has been a bug in that comparison code that really lead to not properly finishing the Result, which, however, should be fixed in the apps >= 4.72.
I am currently taking a look at the parameter sets involved and will try to further track this.
For now be informed that in rare cases it may happen that the process counter may stay at 100% for quite a while. And please continue to inform us of WUs causing that behavior.
If you see such a result and data transfer sizes are not much of an issue to you it would help us if you could zip (or tar/gzip) your BOINC directory (or the projects/einstein and the appropriate slots directory) and make it available to us (before aborting the result or resetting the project).
> I have an endless loop in
)
> I have an endless loop in "H1_0059.9__0060.0_0.1_T05_Test02" after 100% + a
> memory leak at now 88MB to be increasing. Pls check it out!
>
> Boinc 4.16 using...Einstein v4.72
>
Same here for result H1_0073.4__0073.8_0.1_T02_Test02_4
using einstein version 4.72, Boinc 4.16.
Not ending result:
)
Not ending result: H1_0059.4__0059.9_0.1_T03_Test02_2
running BOINC 4.15, Einstein 4.72
Meanwhile it uses nearly 120 MB of memory
Supporting BOINC, a great concept !
Ouch! Thanks for the reports,
)
Ouch! Thanks for the reports, keep up, we are working on it...
There's always one bug left...
BM
BM
I'm having the same problem
)
I'm having the same problem with H1_0073.4__0073.8_0.1_T04_Test02_3
The even bigger problem is that it is running alongside seti@home and predictor. When the work unit gets suspended, it shows 8.5 hours of CPU time. Next time the einstein project comes up, the CPU time drops down to 7.something hours which would seem to indicate that the progress isn't being recorded while the infinite loop is in progress so the unit would likely never reach the maximum FLOPS.
I'm running /dev/null@home! :)
A member of The Knights Who Say Ni!
My BOINC stats page
Sorry folks, I know this is
)
Sorry folks, I know this is annoying. But we always stated that this is alpha test, no guarantees for nothing - and we are working on it.
BM
BM
Honza: > Same here for
)
Honza:
> Same here for result H1_0073.4__0073.8_0.1_T02_Test02_4
> using einstein version 4.72, Boinc 4.16.
Hm, seems that this result has been finished correctly... did you terminate it or was it just taking a long time in 100%?
BM
BM
> Honza: > > > Same here for
)
> Honza:
>
> > Same here for result H1_0073.4__0073.8_0.1_T02_Test02_4
> > using einstein version 4.72, Boinc 4.16.
>
> Hm, seems that this result has been finished correctly... did you terminate it
> or was it just taking a long time in 100%?
>
> BM
Sorry for not reporting final outcome. I suspended this particular WU by BOINC Manager so Einstein took another one. Finally, i let it run overnight and according to BOINCView - it took another extra hour of computing time and uploaded.
Thanks. Actually the
)
Thanks.
Actually the current WUs crunch in three steps: Two doing the analysis of the detector data (shown as 0-50% and 50.01-100%) and then we do a step that does a comparison of some sort. The last step we thought should not take enough time to give it a full % of the progress, but apparently there are cases in which it takes quite longer than we expected.
In addition to that there has been a bug in that comparison code that really lead to not properly finishing the Result, which, however, should be fixed in the apps >= 4.72.
I am currently taking a look at the parameter sets involved and will try to further track this.
For now be informed that in rare cases it may happen that the process counter may stay at 100% for quite a while. And please continue to inform us of WUs causing that behavior.
BM
BM
Okay, I resetted my project,
)
Okay, I resetted my project, because the WU was 5 hours over time. So, next time, I will only have to wait (and say "Hey, it's happening again ;-) )
Supporting BOINC, a great concept !
If you see such a result and
)
If you see such a result and data transfer sizes are not much of an issue to you it would help us if you could zip (or tar/gzip) your BOINC directory (or the projects/einstein and the appropriate slots directory) and make it available to us (before aborting the result or resetting the project).
BM
BM