It appears that I have all LL tests assigned that are likely to be poached real soon now, so that's probably an isolated event.

Now I have 5 TF assignments that are completed by somebody else, what is going on here?

Same here.
 

PROCESSING RESULT: M60160447 HAS A FACTOR: 2599255729428590429303 ERROR CODE: 40, ERROR TEXT: FACTORING RESULT FOR M60160447 WAS NOT NEEDED

[QUOTE=BigBrother;319366]Now I have 5 TF assignments that are completed by somebody else, what is going on here?[/QUOTE]

What exponents?
[QUOTE=swl551;319370]PROCESSING RESULT: M60160447 HAS A FACTOR: 2599255729428590429303 ERROR CODE: 40, ERROR TEXT: FACTORING RESULT FOR M60160447 WAS NOT NEEDED[/QUOTE]

[URL="http://www.mersenne.ca/exponent.php?exponentdetails=60160447"]James' site [/URL]shows you did the work, are you sure you didn't do it twice?

I did factor it twice. {I retract my assertion of GPU72 having fault}
 

[QUOTE=flashjh;319371]What exponents?


[URL="http://www.mersenne.ca/exponent.php?exponentdetails=60160447"]James' site [/URL]shows you did the work, are you sure you didn't do it twice?[/QUOTE]


I have been playing around endlessly with my factors testing MISFIT. Including touching the first row of my factor files..

Forget I ever submitted an entry on the forum regarding this... IT NEVER HAPPENED.:no:

I just updated MISFIT to detect duplicate exponents as part of the UpdateGridStats function. This will help me identify this condition at the local level.

[QUOTE=flashjh;319371]What exponents?[/QUOTE]
59641033 59641111 59641199 59641259 59641297
All handed in before I did by Kyle Askin.

That's bad luck...

Maybe a warning would be better:
*Warning: Poachers are shot on sight.
* Survivors will be shot again.

[QUOTE=sonjohan;319411]That's bad luck...

Maybe a warning would be better:
*Warning: Poachers are shot on sight.
* Survivors will be shot again.[/QUOTE]

...A Warning? Are you sure it was his fault and not gpu72's??:loco:

[QUOTE=kracker;319416]...A Warning? Are you sure it was his fault and not gpu72's??:loco:[/QUOTE]
Kyle Askine does not seem to be a poacher. He is a old contributor and has a nice web page linked to his name on the gimps server :razz:, anyhow he seems a honorable guy to me, so my money are on some gpu72 babble...

[QUOTE=BigBrother;319394]59641033 59641111 59641199 59641259 59641297
All handed in before I did by Kyle Askin.[/QUOTE]

Sorry for my silence everyone; stupid busy with my SFM project... Currently spending more time "in the field" taking pictures of building sites than at a console.

With regards to this problem, it appears to have been a situation where Kyle was assigned these over thirty days ago (2012-10-21 13:45:39 to be exact), but the system then recycled them because they were "late" and weren't "extended".

Then you (BB) were assigned them, but then Kyle submitted results.

Sorry about that. I don't really know what I can do in such situations. Suggestions welcome.

[QUOTE=chalsall;319525]Suggestions welcome.[/QUOTE]
Don't let assignments expire. We don't have any pressure to finish them quickly (at least not anymore). You can still refuse to assign new tasks if aged assignments exist for the account.

I guess you have a pretty long exception list anyway. You could also put all long-time-contributors onto this list ...