After a quite afternoon the aborting has started again.Have again NNT.

Michael

I have now set Beta again to no new tasks. For the whole day while I've been at work it's been sending and cancelling the same tasks all the time, over and over again. It now says on the page "All tasks for computer 57176" that I have tasks that I certainly not have because they've been cancelled over and over again. They aren't on my computer for sure.

I give up on Beta for now. I'll crunch what I have, and will stay as no new tasks until I'm sure the problem is fixed. Having to download the same tasks over and over again, is certainly not good for the bandwidth utilization.

Whatever the problem is, despite what Eric said yesterday, it is not fixed.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

I re-enabled work requests and got my two 'completed' AP Wu's resent, I'll do them again and report them today,

Claggy

They have completed and reported O.K this time,

Claggy

Sten-Arne wrote:

...
Whatever the problem is, despite what Eric said yesterday, it is not fixed.

Agreed, I'm still getting <result_abort_if_not_started> on my tasks for WUs 3981229, 3985904, 3985965, 3990043, and 4006528 even though none of them have been resolved. If any had a canonical result chosen, then it would be as designed for the server to say the work was no longer needed.

Although this isn't quite the kind of Beta testing we'd planned on doing, as Eric pointed out it's much better the problem showed up here than at main. I'll admit it gives me a curiosity itch which is frustrating because there's no way to scratch.

The 4 tasks I noted as having been expired in my message 42794 yesterday were revivified by the script again, so I repeated that 5 step procedure and 3 were resent, 1 expired this time. So of the 11, only WU 3986932 remains out of my reach. That one is resolved, and it would be sensible for the servers to not send it again. But if the script pulls it back up I'll try to get it again tomorrow.

                                                                  Joe

Resumed downloads. Seems okay. have updated several times no cancellations or abortions so far.

Michael

Resumed downloads. Seems okay. have updated several times no cancellations or abortions so far.

Michael

Bah, I was fooled twice into believing that it worked. Now I will stay NNT until at least the year 2023.

LOL

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Resumed downloads. Seems okay. have updated several times no cancellations or abortions so far.

Michael

Bah, I was fooled twice into believing that it worked. Now I will stay NNT until at least the year 2023.

LOL

Newly split work seems OK, but I bet a reissue of one of the affected WUs would still be a problem.

2013 should be adequate, what's the extra 10 years for? ;^)

                                                                   Joe

Resumed downloads. Seems okay. have updated several times no cancellations or abortions so far.

Michael

Bah, I was fooled twice into believing that it worked. Now I will stay NNT until at least the year 2023.

LOL

Newly split work seems OK, but I bet a reissue of one of the affected WUs would still be a problem.

2013 should be adequate, what's the extra 10 years for? ;^)

                                                                   Joe

The extra 10 years is just to be extra extra sure that it doesn't happen again :-)

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Bah, I was fooled twice into believing that it worked. Now I will stay NNT until at least the year 2023.

LOL

Newly split work seems OK, but I bet a reissue of one of the affected WUs would still be a problem.

2013 should be adequate, what's the extra 10 years for? ;^)

                                                                   Joe

The extra 10 years is just to be extra extra sure that it doesn't happen again :-)

LoL, my ability to plan ahead is about as good as the weather forecasts...

I was right about the problem still applying on reissues, see WU 3981430. But I did start it on 51696 before another request, so hope to resolve it by tomorrow.

                                                                  Joe

OK, I got another batch of those ugly cancellations today, driving my quota and consecutive valid tasks down considerably.

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=3981525

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=3982512

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=3981287

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=3984040

http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=3981552

Surely, we must come to the end of this soon...

I have a number that will get aborted if i report them again too (I did a bit of client_state.xml editing to unabort them!!)

Claggy

I have a number that will get aborted if i report them again too (I did a bit of client_state.xml editing to unabort them!!)

Claggy

Well, it sure seems to take awhile to get them all out of the system. Pity, that the server cancellations of these WU's affect the quota though.