[QUOTE=tha;483083]What would be desired is the server accepting the new B1/B2 limits.[/QUOTE]

I suspect that if you had done the test with known factors in quotation marks, and it reported no factor, then the B1,B2 would at least show up in the history, even though Primenet gives no credit due to "result not needed".

Or at least that's the way I recall it used to work.

[QUOTE=GP2;483098]I suspect that if you had done the test with known factors in quotation marks,...[/QUOTE]

That is exactly what I was able to do during the last run.

[QUOTE=tha;483104]That is exactly what I was able to do during the last run.[/QUOTE]

The exact job I asked one of my machines to do was: [code]Pminus1=N/A,1,2,22351237,-1,400000,9000000,134107423,1564586591,3889115239,6403852912871,55203442762393[/code]

And it diligently refound some factors already known.

[QUOTE=chalsall;483106]And it diligently refound some factors already known.[/QUOTE]

That's because you forgot the quotation marks:

[code]Pminus1=N/A,1,2,22351237,-1,400000,9000000,"134107423,1564586591,3889115239,6403852912871,55203442762393"[/code]

Are any further tests desired to resolve this issue?

[QUOTE=GP2;483116]That's because you forgot the quotation marks:[/QUOTE]
[QUOTE=tha;483515]Are any further tests desired to resolve this issue?[/QUOTE]
Yeah, we took Chris and beat him hard so next time he remember the quotes...

[QUOTE=LaurV;483635]Yeah, we took Chris and beat him hard so next time he remember the quotes...[/QUOTE]

I meant the original issue, getting new B1/B2 values accepted by the server, even if a factor for that exponent already exists.

forgotten or orphan assignments
 

It seems one of the [url=https://www.mersenne.org/thresholds/]PrimeNet Assignment Rules[/url] is not enforced :[code]PrimeNet Assignment Rules
Since PrimeNet began, the server has recycled exponents where the client
computer is 60 days past due in updating the server. This rule has been
fairly effective and will continue.[/code]I queried the current active assignments. I excluded the ranges where there are too many active assignments because of the limit in the query page. I found more than 1700 that were more than 60 days late reporting. A lot of them are obviously forgotten assignments : probably on a machine that crashed and was reinstalled or scraped.

I think a query should be run regularly over the whole 0 to 1000M range to eliminate active assignments that are more than 60 (or being generous 90) days late. Such a query does not need to run daily, monthly is more than enough, especially after the first run.

Jacob

[QUOTE=S485122;483862]I queried the current active assignments. I excluded the ranges where there are too many active assignments because of the limit in the query page. I found more than 1700 that were more than 60 days late reporting[/QUOTE]

Have you excluded manual assignments from this list? Also, are these all LL tests? Or are there PRP cofactor tests in there as well?

[QUOTE=axn;483863]Have you excluded manual assignments from this list? Also, are these all LL tests? Or are there PRP cofactor tests in there as well?[/QUOTE]DVRA LEX SED LEX.
The rules apply to all and everything : even manual assignments (they can extend their assignments up to 3 years or more !). But if you look at the active assignments yourself, you will see that it is clearly a problem of forgotten/orphan assignments.

Jacob

[QUOTE=S485122;483862]I think a query should be run regularly over the whole 0 to 1000M range to eliminate active assignments that are more than 60 (or being generous 90) days late. Such a query does not need to run daily, monthly is more than enough, especially after the first run.[/QUOTE]

Does it [i]really[/i] need to be run over the entire range up to 1 billion?

Consider [M]M332,197,123[/M]. Someone supposedly started a manually-assigned double-check, although with zero progress and no updates since it was assigned two-and-a-half years ago.

It probably wouldn't be scheduled for a normal double check until the 2030s. Anyone who wanted to could poach it, or maybe a result will miraculously be returned in the meantime.

But does it really matter if we let that ghost assignment linger? We only need to expire forgotten assignments in active ranges, where they're actually holding up progress.