yCruncher wrapper is not working

[Argyrum]

The y-Cruncher wrapper seems to not detect when the tests are done and just lets the program run.

Logs: CoreCycler_2025-10-25_13-00-23_YCRUNCHER_19-ZN2 ~ KAGARI.log yCruncher_2025-10-25_13-00-23_mode_19-ZN2 ~ KAGARI.log

Disabling the wrapper and relying on CPU utilization detection does work: enableYCruncherLoggingWrapper = 0 Using a 7900X and W10, seen in both the latest alpha (0.11.0.0a4) and stable (0.10.0.0) versions.

Config is the built-in quick-initial-test.yCruncher.config.ini

[General]
stressTestProgram = YCRUNCHER
runtimePerCore = auto
suspendPeriodically = 1
coreTestOrder = Default
skipCoreOnError = 1
numberOfThreads = 2
restartTestProgramForEachCore = 1
delayBetweenCores = 5

[yCruncher]
mode = 19-ZN2 ~ Kagari
tests = SFTv4, FFTv4, N63
testDuration = 20

Observations: I don't know if it might be related, but I've seen that y-Cruncher SFT (not v4) seems to error out far more when running with the wrapper than without.

[sp00n]

Hm, according to the log the script didn't do anything after the first parsing of the y-cruncher output and the (manual?) termination of the script

              +++ 13:00:40 - Getting new log file entries
              +++            Getting new log entries starting at position 0 / Line 0
              +++            The new log file entries:
              +++            - [Line 1] 
              +++            - [Line 2] 
              +++            - [Line 3] 2025-10-25 13:00:27
              +++            - [Line 4] 
              +++            - [Line 5] Checking processor/OS features...
[...]
              +++            - [Line 57] Running SFTv4: 
              +++            New file position: 1857 / Line 57
              +++ 13:02:18 - Automatic runtime per core selected
              +++            No passed tests found yet, assuming we're at the very beginning of the run
              +++ 13:05:31 - Checking for stress test errors
              +++            Checking the new y-cruncher log entries...
              +++ 
              +++ ┌─────────────────────────┐
              +++ │    THE FINALLY BLOCK    │
              +++ └─────────────────────────┘
              +++ 
              +   13:05:42 - Terminating the script...

I've seen this happen if you accidentally trigger the quick edit mode by selecting a character with the mouse inside the terminal window, which causes any script to stop execution. However it shouldn't really happen with the Terminal application you're using the in screenshot, only with the "legacy" command window prompt (the one without tabs), so I'm not entirely sure what happened there for you. Is that happening consistently for you?

[Argyrum]

Hi, I tried running CMD in both the Windows Terminal and standalone, but in either case it consistently does not stop until manually told to (Ctrl+C) if the wrapper is enabled. I took care to not select any text and also tried to not bring yCruncher to the foreground, but the result is the same. The wrapper itself seems to work since the log file (yCruncher_*.log) contains all the text generated by yCruncher until the moment it is terminated, so the issue seems to be around corecycler catching the error/iteration end in said log.

The same can be seen in the original log files attached:

CoreCycler_*.log:

+++ 13:00:40 - Getting new log file entries +++ Getting new log entries starting at position 0 / Line 0 +++ The new log file entries: +++ - [Line 1] (...) +++ - [Line 54] Iteration: 0 Total Elapsed Time: 0.031 seconds ( 0.001 minutes ) +++ - [Line 55] +++ - [Line 56]
+++ - [Line 57] Running SFTv4: +++ New file position: 1857 / Line 57 +++ 13:02:18 - Automatic runtime per core selected <-- Why wait 2 minutes? Iteration is already done by then +++ No passed tests found yet, assuming we're at the very beginning of the run +++ 13:05:31 - Checking for stress test errors <-- There were no errors, so it makes sense it didn't catch anything +++ Checking the new y-cruncher log entries... +++ ┌─────────────────────────┐ +++ │ THE FINALLY BLOCK │ +++ └─────────────────────────┘

• 13:05:42 - Terminating the script...

yCruncher_*.log:

2025-10-25 13:00:27 Checking processor/OS features... (...) Iteration: 0 Total Elapsed Time: 0.031 seconds ( 0.001 minutes ) Running SFTv4:
Running SFTv4: Passed Test Speed: 4.96 * 10^09 bits / sec

Running FFTv4: Running FFTv4: Passed Test Speed: 3 * 10^09 bits / sec

Running N63: Running N63: Passed Test Speed: 5.84 * 10^08 bits / sec

Iteration: 1 Total Elapsed Time: 61.162 seconds ( 1.019 minutes ) <-- Should've been detected and switched core Running SFTv4: Running SFTv4: Passed Test Speed: 5.22 * 10^09 bits / sec

Running FFTv4: Running FFTv4: Passed Test Speed: 3.01 * 10^09 bits / sec

Running N63:
Running N63: Passed Test Speed: 5.84 * 10^08 bits / sec

(...)

Iteration: 5 Total Elapsed Time: 301.621 seconds ( 5.027 minutes ) <-- Went until Iteration 5 and still nothing Running SFTv4: (Manually terminated from main script)