was P-1 expired?

[dh1]

this P-1 result appears to have been marked expired? why or what the read "Assigned" area means?
http://www.mersenne.org/report_expon...exp_hi=&full=1 thanks.

[GP2]

Maybe somehow you were doing two identical P−1 tests at the same time on the same exponent, with the same B1 and B2 parameters, so when one completed the other automatically expired?

[Prime95]

Maybe when you checked in the result (either automatic or manually), the assignment ID either was not reported or the lookup failed. Then when the result is reported the assignment would be marked as expired due to poaching.

[chalsall]

Originally Posted by Prime95

Maybe when you checked in the result (either automatic or manually), the assignment ID either was not reported or the lookup failed. Then when the result is reported the assignment would be marked as expired due to poaching.

This comes across a bit like a "Star Trek: The Next Generation" episode. Maybe somehow something happened which we don't fully understand but could possibly explain what happened.

You have the logs. Drill down.

[ET_]

Originally Posted by chalsall

This comes across a bit like a "Star Trek: The Next Generation" episode. Maybe somehow something happened which we don't fully understand but could possibly explain what happened.

You have the logs. Drill down.

Whch episode?

[chalsall]

Originally Posted by ET_

Whch episode?

Almost all of the latter episodes where Data malfunctions (yet again) and the producers relied on Brent Spiner's acting ability to carry the show.

As much as I enjoyed STNG, it wasn't B5.

[Madpoo]

Originally Posted by chalsall

This comes across a bit like a "Star Trek: The Next Generation" episode. Maybe somehow something happened which we don't fully understand but could possibly explain what happened.

You have the logs. Drill down.

You, sir, are a harsh taskmaster! LOL

I looked at the logs and it looks like it did include the assignment ID. I don't know if P-1 results have to match things exactly according to what was assigned? I'm clueless on that.

Whatever the case, it seems like it checked in okay but instead of deleting the assignment, it expired it, so it sure seems like it thought something about what was checked in was different than what was assigned, but I have no idea what or if that's even the case.

[Syntony]

Originally Posted by Madpoo

...I don't know if P-1 results have to match things exactly according to what was assigned?
...

Apparently not, as I frequently check in P-1 assignments with higher B1, B2 bounds than those assigned and the server seems perfectly happy with them...

[lycorn]

Originally Posted by Syntony

Apparently not, as I frequently check in P-1 assignments with higher B1, B2 bounds than those assigned and the server seems perfectly happy with them...

Yep. Same here, with ECM.

[mattmill30]

Originally Posted by Madpoo

You, sir, are a harsh taskmaster! LOL

I looked at the logs and it looks like it did include the assignment ID. I don't know if P-1 results have to match things exactly according to what was assigned? I'm clueless on that.

Whatever the case, it seems like it checked in okay but instead of deleting the assignment, it expired it, so it sure seems like it thought something about what was checked in was different than what was assigned, but I have no idea what or if that's even the case.

This seems similar to the issue I reported for M74759323. The assignment continued to appear as a manual assignment within my CPU list, but wasn't present on the assignments screen. I can't remember whether the 'expired' symptom also occured.
I am seeing my same issue with M116539543, where it still appears within CPUs as a Manual Assignment and not assignments, but it isn't demonstrating the 'expired' symptom.