Incorrect core labeling for errors

[mooman219]

For at least ycruncher, if the core fails right around when the cycle is ending, CoreCycler may count it as a failure for the next core. I've had a failing core (10) for several cycles, so I decided to start on the core and watch it, but it seemed to not error as previous runs suggested it did. I tested the core that runs (2) before it, and that core was failing right at the end of its 20 minute test every time. By the time CoreCycler registered the CPU power, it had already moved on to the next core and then counted the failure for that one.

Do you recommend restartTestProgramForEachCore=1 to resolve this?

[sp00n]

Do you have the log files for these runs?

[sp00n]

Closing due to inactivity