Stranded assignment?

[cardogab7341]

I got an assignment (54621293) that shows up on my GPU72 assignments page as an LL assignment, but it is not assigned to any of my CPUs, just "manual" like my TF assignments. Also it does not show up on my Primenet LL assignments, and it does not show up on any of my mfaKtc worktodo files. I guess I'll un-assign it since if I leave it it will never get done. I'm just wondering how it got to this state.

[petrw1]

Originally Posted by cardogab7341

I got an assignment (54621293) that shows up on my GPU72 assignments page as an LL assignment, but it is not assigned to any of my CPUs, just "manual" like my TF assignments. Also it does not show up on my Primenet LL assignments, and it does not show up on any of my mfaKtc worktodo files. I guess I'll un-assign it since if I leave it it will never get done. I'm just wondering how it got to this state.

If it is Manual then when you finish it you need to submit the Manual results as directed here:

http://www.mersenne.org/manual_result/

[cardogab7341]

I did not get it manually. I get my LL assignments through Prime95 via the GPU72 proxy, so that is why I don't know how it got there. All of my manual assignments are for TF through MISFIT.

[S485122]

Obviously this is a GPU72 problem and not a Primenet one. It should have been posted in the relevant thread.

Jacob

[chalsall]

Originally Posted by S485122

Obviously this is a GPU72 problem and not a Primenet one. It should have been posted in the relevant thread.

Hmmmm...

The database does show this assigned to you (2014-05-07 23:50:43 UTC), but without an update. Further, Primenet shows it being assigned to one of my spiders, and the assignment record is showing a "Reclaimed" warning state (this happens when the spider is assigned a candidate by Primenet which GPU72 believes is already "owned" by one of its users).

This suggests it was a communications error between your Client and the Proxy. As in, the request came into the proxy and was passed to Primenet for fulfillment. But then the client didn't report an expected completion time, which it should have done immediately after -- probably because it never received the assignment message.

Short version: this will happen from time-to-time (thankfully rarely) because of networking issues. Feel free to delete it from your GPU72 account.

[petrw1]

For the record I get the odd GPU72 assignment with all date/time columns blank on the list....I just unassign these. < 1/100.

[cardogab7341]

Originally Posted by chalsall

Hmmmm...

The database does show this assigned to you (2014-05-07 23:50:43 UTC), but without an update. Further, Primenet shows it being assigned to one of my spiders, and the assignment record is showing a "Reclaimed" warning state (this happens when the spider is assigned a candidate by Primenet which GPU72 believes is already "owned" by one of its users).

This suggests it was a communications error between your Client and the Proxy. As in, the request came into the proxy and was passed to Primenet for fulfillment. But then the client didn't report an expected completion time, which it should have done immediately after -- probably because it never received the assignment message.

Short version: this will happen from time-to-time (thankfully rarely) because of networking issues. Feel free to delete it from your GPU72 account.

OK, I'll un-assign it and watch for this in the future.

Thanks.