"Poached" with a result, the day after receiving an assignment

[kriesel]

In my prime.log on Falcon, an i7-7500U laptop allocated to first-time LL testing stragglers/expirations (intended to pick up unassigned exponents for the next first-test milestone):

[Wed Nov 20 06:55:38 2019 - ver 29.8]
Getting assignment from server
PrimeNet success code with additional info:
Server assigned Lucas Lehmer primality test work.
Got assignment A086A26D761048A63E9F39549B3B____: LL M88104427
Sending expected completion date for M88104427: Dec 10 2019

THE NEXT DAY, an LL test result is reported by _DJ3D_
https://www.mersenne.org/report_expo...8104427&full=1
causing my work in progress to be reclassified as a double-check. And it's not like there was a milestone at stake; 89 million will be next year.
Oh well. What goes around, comes around. And _DJ3D_ may have had an assignment initially and finished shortly after it expired. Meanwhile, a couple of exponents for the current, 87 million milestone remain unassigned.

[Madpoo]

Originally Posted by kriesel

... And _DJ3D_ may have had an assignment initially and finished shortly after it expired. Meanwhile, a couple of exponents for the current, 87 million milestone remain unassigned.

That's what happened. They had an assignment from July 24th and it just took a couple days longer to finish than what the assignment allowed.

I've been wondering about the two unassigned exponents in the 86M-87M range. They're available for assignment so I guess it's just that no cat 0 capable systems have snatched them up? They are 86789597 and 86789621

[ATH]

Originally Posted by Madpoo

I've been wondering about the two unassigned exponents in the 86M-87M range. They're available for assignment so I guess it's just that no cat 0 capable systems have snatched them up? They are 86789597 and 86789621

Yoink!