Stranded assignment.
 

I pulled 2 LLs from the vault but they were only factored up to 72. I factored them to 73 before I LL'd them and sure enough, one of them coughed up a factor:
49325909 F-PM1 2013-01-19 04:41 4997955263608273662463

Prime95 Canceled it off my todo list when it updated, but I've still got in on gpu to 72. Do I just unreserve it and it will fall off? It shouldn't be reassigned.

Please advise.

To avoid bothering PrimeNet server too much, GPU72's spiders do not inquire it so often. Sooner or later they will detect that the work was done and you will be credited, assuming you did the work that you pledged (partial bit levels are not credited, until you finish the bitlevel you reserved for that exponent).

[QUOTE=Aramis Wyler;325194]I pulled 2 LLs from the vault but they were only factored up to 72. I factored them to 73 before I LL'd them and sure enough, one of them coughed up a factor: 49325909 F-PM1 2013-01-19 04:41 4997955263608273662463[/QUOTE]

Lucky you! :smile:

The system only watches for the completion of the work assigned. As these were assigned as LLing, that's what it was watching for. And, to be perfectly honest, I never thought about people doing additional TFing -- but obviously I should have.

I've changed that assignment to be TF work, and had "Spidy" scan that range. The work has been detected and credited to your account, and the assignment removed.

So wow, I've been so preoccupied with the need to get p-1 work completed that it's been almost a year since I reserved a LL test. It looks like spidey has been improved somewhat since the last time though! I pulled 4 numbers, factored them from 72 to 74, and coughed up a factor for one of them. When I then unreserved that exponent in prime95 I got an unexpected response:
[Wed Nov 27 07:21:38 2013 - ver 27.9]
Unreserving assignment 422336585552900C6F9050598FF98B71
PrimeNet error 43: Invalid assignment key
au: no such assignment key, GUID: eaeb5c01998d5f94a112735e0bfc18f6, key: 422336585552900C6F9050598FF98B71

and got a new assignment. I see the old one was removed from my assignment list. I'm just posting the note because I'm curious if the assignment would have been removed from my queue at the next check in if I hadn't unreserved it, and because I was surprised both that spidey noticed that the factor was found and that, it having noticed that, didn't credit me for finding a factor. :grin:

I don't need credit for finding the factor or for doing tf from 72-74 on each of the ll tests I pulled, but I thought the sequence of events was unexpected enough that some clarification might be in order on the forums and wanted to make sure gpu72 wouldn't reassign [SIZE=2]53972629[/SIZE].

[QUOTE=Aramis Wyler;360431]I don't need credit for finding the factor or for doing tf from 72-74 on each of the ll tests I pulled, but I thought the sequence of events was unexpected enough that some clarification might be in order on the forums and wanted to make sure gpu72 wouldn't reassign [SIZE=2]53972629[/SIZE].[/QUOTE]

Thanks for bringing this forward.

According to my records, this candidate was assigned to you (at 2013-11-27 02:29:50 UTC) to LL.

"Spidy" then noticed that it had been factored (it didn't determine by whom) at 2013-11-27 12:22:21 UTC, and flagged it with a warning code.

Short version: GPU72 expects that people do what they've been assigned. TFing LL assignments is fine, but the system doesn't give credit (although it will notice and warn).