Usually after optimizer or re-tester has failed to 'hook up'...this is random. I have posted before about this in previous versions. It will hang on zero % forever, when you hit stop, it stops and reports how far it had got in the % bar...it just wasn't reporting this as it progressed.
Few restarts (hitting stop, start a few times) and it hooks up, but will sometimes then complete with a value of over 100%.
All this makes it difficult to trust whats going on under the hood and the results produced.
Attachment M1 Simulated WF Only.jpg added
Stays like this with 0% progress for 6 minutes, but with the processors clearly busy...then 6 minutes in suddenly jumps directly to 100% and complete. Running Time and Estimated Time to completion remain at zero for the entire time.
I think now that its doing its job, its just that the progress bar and time duration/to completion don't work.
In builder this issue is not present, and 100% processors usage is attained and maintained from the the get go.
I also check the optimiser and ran the same walk forward in the optimiser...it worked fine, tests began immediately with 100% processor usage from the get go.
The issue is confined to the Retester using walk forward or optimisation profile/paramteter permutation cross checks.
Status changed from Waiting for information to Fixed
I'll check it, but the problems you describe are most probably caused by starting Retester again when it wasn't fully stopped.
It has no effect on backtesting reliability itself, every backtest is completely separated and not influenced by another possibly running from previous retest.