PRP DC being processed as PRP

[kriesel]

I have set a system's prime95 to prefer PRP DC to help with the dearth of PRP DC results. (See https://www.mersenneforum.org/showth...901#post533901)
I note this morning that a recent assignment to https://www.mersenne.org/report_expo...1889037&full=1 is marked as PRP and given 7 days to report progress. This exponent already has a PRP result, so this would/should have been issued as PRP DC, and should be summarized as one. But it is being shown as a PRP first test instead, on the exponent status page, and on my accounts assignments page. It's listed as a Cat 0 PRP there, estimated time to complete 33 days, time to expiration 7 days. From prime.log:

[Wed Jan 01 19:06:48 2020 - ver 29.8]
Updating computer information on the server
Sending expected completion date for M89210659: Jan 07 2020
Sending expected completion date for M90081949: Jan 21 2020
Sending expected completion date for M88905497: Jan 02 2020
Getting assignment from server
PrimeNet success code with additional info:
Server assigned PRP work.
Got assignment (redacted aid): PRP M81889037

This is a known issue that was reported months ago. Please fix it. See also https://www.mersenneforum.org/showthread.php?t=24942

A counterexample is https://www.mersenne.org/report_expo...9335979&full=1 which is a triple check, correctly listed as PRP-D, cat 4. From prime.log:

[Wed Mar 27 18:15:20 2019 - ver 29.4]
Exchanging program options with server
[Thu Mar 28 03:37:00 2019 - ver 29.4]
Getting assignment from server
PrimeNet success code with additional info:
Server assigned PRP work.
Got assignment (redacted aid): PRP M79335979

Maybe this one got manually tweaked on the PrimeNet server after the fact?

Note also that prime95 v29.8b6 misreports the PRPDC assignment as PRP in the Status output. The local worktodo correctly shows PRPDC=.

PRPDC=(aid redacted),1,2,81889037,-1,75,0,3,1

The local worktodo containing PRPDC= confirms that the assignment was made as PRP DC, and both PrimeNet and prime95 are misrepresenting it as PRP instead.

[kriesel]

Please fix the PrimeNet server's mishandling of PRP DC assignments as if they were first-time assignments.
With PRP DC work preference in latest available prime95 version 29.8b6, PRP DC cat 4 work issued by PrimeNet, are mishandled by the PrimeNet server as PRP cat 0 first-time assignments, with short expiration period, and display as PRP not PRP-D. In my assignments status page:
82655831 indicated as cat 0 PRP, 5 days to go, expires in 1
82703021 indicated as cat 0 PRP, 9 days to go, expires in 7
Manual extension is ineffective as a workaround

Assignments are incorrectly listed as PRP on https://www.mersenne.org/workload/

PRP=(aid),1,2,82655831,-1,75,0,3,1
PRP=(aid),1,2,82703021,-1,75,0,3,1

but are correctly listed as PRP DC in the prime95 worktodo.txt on the client system:

[Worker #1]
PRPDC=(aid),1,2,82703021,-1,75,0,3,1

[Worker #2]
PRPDC=(aid),1,2,82655831,-1,75,0,3,1

This old system is crunching them as fast as it can. It's doing PRP DC partly because with other workloads it's not fast enough for PRP assignments.

The prime95 instance's prime.log also shows they were PRP DC assignments when issued:

[Fri Feb 28 14:31:21 2020 - ver 29.8]
Updating computer information on the server
Sending expected completion date for M80289031: Mar 05 2020
Sending expected completion date for M82353587: Feb 29 2020
Getting assignment from server
PrimeNet success code with additional info:
Server assigned PRPDC work.
Got assignment (aid): PRP M82655831
Sending expected completion date for M82655831: Mar 17 2020

[Thu Mar 05 04:39:47 2020 - ver 29.8]
Getting assignment from server
PrimeNet success code with additional info:
Server assigned PRPDC work.
Got assignment (aid): PRP M82703021
Sending expected completion date for M82703021: Mar 23 2020

They could not have been PRP first test assignments when made, since each had a PRP result already long before when these assignments were made.
https://www.mersenne.org/report_expo...exp_hi=&full=1 (2018-12-02)
https://www.mersenne.org/report_expo...exp_hi=&full=1 (2018-03-20)

See also https://www.mersenneforum.org/showpost.php?p=534689&postcount=445,
https://www.mersenneforum.org/showpost.php?p=534995&postcount=453