It got stuck running benchmark this morning at 5am. "Pausing worker to run the needed benchmarks". It was doing P+1 on 31M (1600K FMA3) with 1 worker 8 cores. Prime95 30.7b1 on Windows 10.

Now 11 hours later when I checked the computer, Prime95 was still using 1 core for something in Task Manager but never ran any benchmarks and no P+1 since 5am. It could not be shut down, had to kill the process in Task Manager.

The file "results.bench.txt" was not updated, I'll see if it happens again tomorrow.

Could it be because it is an old long "results.bench.txt" file at 383 KB going back to April 2019 ?

[QUOTE=ATH;589289]It got stuck running benchmark this morning at 5am.[/QUOTE]

A line of code mysteriously disappeared. I'll upload fixed executables today.

I have this in my screen output for every result:
[CODE]
[Work thread Oct 3 14:23] M9141287 stage 2 complete. 9147452 transforms. Total time: 2390.486 sec.
[Work thread Oct 3 14:23] Stage 2 GCD complete. Time: 1.301 sec.
[Work thread Oct 3 14:23] M9141287 completed P-1, B1=2000000, B2=162000000, Wi8: E5571098
[Comm thread Oct 3 14:23] Sending result to server: UID: Tha/Z170-m30.7, M9141287 completed P-1, B1=2000000, B2=162000000, Wi8: E5571098
[Comm thread Oct 3 14:23]
[Comm thread Oct 3 14:23] URL: http://v5.mersenne.org/v5server/?v=0.95&px=GIMPS&t=ar&g=df88abe73833aa676d31a0bf32b0d492&k=0&m={"status":"NF",+"exponent":9141287,+"worktype":"P-1",+"b1":2000000,+"b2":162000000,+"fft-length":491520,+"security-code":"E5571098",+"program":{"name":"Prime95",+"version":"30.7",+"build":1,+"port":8},+"timestamp":"2021-10-03+12:23:14",+"user":"Tha",+"computer":"Z170-m30.7"}%0A&r=5&d=1&A=1&b=2&n=9141287&c=-1&B1=2000000&B2=162000000&fftlen=491520&ss=59330&sh=AE771A6DD8A50DE4365D285900BB3A12
[Work thread Oct 3 14:23]
[Work thread Oct 3 14:23] P-1 on M9141317 with B1=2000000, B2=TBD

[/CODE]

[QUOTE=Prime95;589305]A line of code mysteriously disappeared.[/QUOTE]

Actually, not a mystery. My text editor begins most commands with ^X (e.g. save file is ^X^S). MS Visual Studio treats ^X as delete the current line. If you then build an executable, Visual Studio saves the file.

I usually catch these fat fingered moments, but this one slipped through undetected. I've taken this moment to change Visual Studio to not map ^X to any commands.

[QUOTE=tha;589313]I have this in my screen output for every result:[/QUOTE]


This behavior did not change to my knowledge. Either don't merge the comm and worker window output or go to Test/Primenet/Connection and turn off "Output debug info to prime.log" (a.k.a. Debug=0 in the [PrimeNet] section of prime.txt).

No CERTS
 

I haven't received any CERTS since updating. I have the box "Get occasional proof certification work" checked. Maybe just a coincidence but I usually get several CERTs a day.

Build 2 with the benchmark fix now ready.

[QUOTE=Prime95;589236]In preferences, set output iterations low -- like 10000.[/QUOTE]

Before running the test, I forgot to change that value (it was 250000). I hope that's okay either way?

CPU: AMD 3800X (Zen 2)
1 Worker, 8 Threads
106M exponent, 5760K FFT
Stage 1: 1100-1120 seconds per output
Stage 2: 1965-1985 seconds per output

I probably should mention that I have Brent-Suyama activated in prime.txt (largely because of personal preference) and that I have doubled tests_saved, is it still helpful or should I run one exponent with default settings?

[QUOTE=Chuck;589332]I haven't received any CERTS since updating. I have the box "Get occasional proof certification work" checked. Maybe just a coincidence but I usually get several CERTs a day.[/QUOTE]

After updating to build 2 I am receiving CERTS again.

[QUOTE=kruoli;589405]Before running the test, I forgot to change that value (it was 250000). I hope that's okay either way?

I probably should mention that I have Brent-Suyama activated in prime.txt (largely because of personal preference) and that I have doubled tests_saved, is it still helpful or should I run one exponent with default settings?[/QUOTE]

That's OK, thanks for the data.

Brent-Suyama is no longer supported. An artifact of the P+1-style stage 2.

[QUOTE=Chuck;589424]After updating to build 2 I am receiving CERTS again.[/QUOTE]

Coincidence.

Win 10
I5-9600K stock frequency



With Prime95 30.7 b2 I have this problem
[QUOTE]

[Oct 4 23:00:26] Waiting 15 seconds to stagger worker starts.
[Oct 4 23:00:42] Worker starting
[Oct 4 23:00:42] Setting affinity to run worker on CPU core #5
[Oct 4 23:00:42] Starting Gerbicz error-checking PRP test of 49923*2^1700000+1 using all-complex FMA3 FFT length 144K, Pass1=768, Pass2=192, clm=2
[Oct 4 23:00:44] ERROR: Comparing Gerbicz checksum values failed. Rolling back to iteration 15.
[Oct 4 23:00:44] Continuing from last save file.
[Oct 4 23:00:44] Resuming Gerbicz error-checking PRP test of 49923*2^1700000+1 using all-complex FMA3 FFT length 144K, Pass1=768, Pass2=192, clm=2
[Oct 4 23:00:44] Iteration: 16 / 1700015 [0.00%].
[Oct 4 23:00:44] Hardware errors have occurred during the test!
[Oct 4 23:00:44] 1 Gerbicz/double-check error.
[Oct 4 23:00:44] Confidence in final result is excellent.
[Oct 4 23:00:45] ERROR: Comparing Gerbicz checksum values failed. Rolling back to iteration 15.
[Oct 4 23:00:45] Continuing from last save file.
[Oct 4 23:00:45] Resuming Gerbicz error-checking PRP test of 49923*2^1700000+1 using all-complex FMA3 FFT length 144K, Pass1=768, Pass2=192, clm=2
[Oct 4 23:00:45] Iteration: 16 / 1700015 [0.00%].
[Oct 4 23:00:45] [I][B][COLOR=Blue]Hardware errors have occurred during the test![/COLOR][/B][/I]
[Oct 4 23:00:45] 2 Gerbicz/double-check errors.
[Oct 4 23:00:45][COLOR=Red][B] Confidence in final result is excellent.[/B][/COLOR]
[/QUOTE]On the other side, with Prime95 30.6 build 4 on same configuration


[QUOTE][Oct 4 23:03:56] Waiting 15 seconds to stagger worker starts.
[Oct 4 23:04:11] Worker starting
[Oct 4 23:04:11] Setting affinity to run worker on CPU core #5
[Oct 4 23:04:11] Starting Gerbicz error-checking PRP test of 49923*2^1700000+1 using all-complex FMA3 FFT length 144K, Pass1=768, Pass2=192, clm=2
[Oct 4 23:04:12] Gerbicz error check passed at iteration 976.
[Oct 4 23:04:12] Gerbicz error check passed at iteration 2000.
[Oct 4 23:04:13] Gerbicz error check passed at iteration 3089.
[Oct 4 23:04:14] Gerbicz error check passed at iteration 4178.
[Oct 4 23:04:15] Gerbicz error check passed at iteration 5334.
[Oct 4 23:04:15] Gerbicz error check passed at iteration 6559.

[/QUOTE]