Script seems to stop when switching CPUs

[ChiefZigZag]

The test ran well on one of my 5900x systems. Last night I decided to push it further and set it to 100m All Prime95. I awoke this morning to see the script was still on Core 0 and Prime95 was still running. I pressed Enter and then it suddenly switched to Core 6. Uncertain to why this has happened but I have seen this happen on another computer but I didn't put much thought into it. There was no Prime95 error but it seemed to have run all night on a single core. Attached is the Log files. Any ideas?

Prime95_2021-05-27_23-22-14_SSE_ALL_FFT_4K-32768K.txt

CoreCycler_2021-05-27_23-22-14_PRIME95_SSE.log

[sp00n]

Probably this issue with console windows in Windows:

https://github.com/sp00n/corecycler/issues/15#issuecomment-815299483

[sp00n]

On the upside, you now have a 6 hour continuous stress test of core #0, which apparently worked just fine. ;)

Also, instead of fixing it to 100 minutes, I'd suggest you use the "auto" setting, which will test all the selected FFT sizes for each core and only move on to the next one when all of them have been tested.

For the select issue, I have no solution program wise, but you can disable the quick edit mode (see the links in the post above).

[ChiefZigZag]

Thanks sp00n, I must of clicked the window. I wonder if there is some sort of fix/work around for this problem. Wasn't aware that Auto would complete all the FFT size.. I'll give it a test and hopefully get all my systems stable!

[sp00n]

Yeah, you're usually not aware of this issue until it happens to you. It was the same for me. It's especially weird because on other OS like Linux this isn't an issue at all. I have included it in the readme.txt though. 😛

But as mentioned in my second post, there's a way to disable this quick edit mode.

[gonzol]

Thank you for your work, the idea is great, but unfortunatelly it doesn't work on windows 7. When runtimePerCore is set to 10s and above it results in script freezing. Nothing helps, Quick mode is disabled. Also checked script under VirtualBox with same results: Windows10 runs fine with any time, Windows7 runs fine only up to 9 seconds. The latest version which doesn't freeze is 0.7.9.2, and I have to use this version.

[sp00n]

Thank you for your work, the idea is great, but unfortunatelly it doesn't work on windows 7. When runtimePerCore is set to 10s and above it results in script freezing. Nothing helps, Quick mode is disabled. Also checked script under VirtualBox with same results: Windows10 runs fine with any time, Windows7 runs fine only up to 9 seconds. The latest version which doesn't freeze is 0.7.9.2, and I have to use this version.

Yes, quite possible. I think I remember reading during development that some instructions used in the script may not be supported in Windows 7 and therefore the whole OS is not supported as well. And I have no plans to change this,