How many units are left from Qsqrt_DS1x5?
I´m just asking, the one unit I got might be faster then units from sf3_SF1x271.
:)

How many units are left from Qsqrt_DS1x5?
I´m just asking, the one unit I got might be faster then units from sf3_SF1x271.
:)

There should be no units left from Qsqrt_DS1x5. There is one long one left on Qsqrt_DS1x8 and a handful of medium length Qsqrt_DS3x8 cases.

... a handful of medium length Qsqrt_DS3x8 cases.

Them's big hands. I've got 11 of them, and I may have to toss back some of the ones that got stuck in a long queue on slower machines.

... a handful of medium length Qsqrt_DS3x8 cases.

Them's big hands. I've got 11 of them, and I may have to toss back some of the ones that got stuck in a long queue on slower machines.

If they have a "k2" at the end of the name, then they could be of the longer running variety (by that I mean several days on a fast computer, not to be confused with the insanely long runners from months ago).

For comparison, the DS11x271 units are averaging about 10 hours.

How many units are left from Qsqrt_DS1x5?
I´m just asking, the one unit I got might be faster then units from sf3_SF1x271.
:)

There should be no units left from Qsqrt_DS1x5. There is one long one left on Qsqrt_DS1x8 and a handful of medium length Qsqrt_DS3x8 cases.

My bad, I meaned DS1x8.

How many units are left from Qsqrt_DS1x5?
I´m just asking, the one unit I got might be faster then units from sf3_SF1x271.
:)

There should be no units left from Qsqrt_DS1x5. There is one long one left on Qsqrt_DS1x8 and a handful of medium length Qsqrt_DS3x8 cases.

My bad, I meaned DS1x8.

You are not on the "no reply" list for the last Qsqrt_DS1x8. If you are still crunching on one of those you might want to abort it and let me know which one so I can credit you.

How many units are left from Qsqrt_DS1x5?
I´m just asking, the one unit I got might be faster then units from sf3_SF1x271.
:)

There should be no units left from Qsqrt_DS1x5. There is one long one left on Qsqrt_DS1x8 and a handful of medium length Qsqrt_DS3x8 cases.

My bad, I meaned DS1x8.

You are not on the "no reply" list for the last Qsqrt_DS1x8. If you are still crunching on one of those you might want to abort it and let me know which one so I can credit you.

It´s completed, faster then I guessed.
http://numberfields.asu.edu/NumberFields/result.php?resultid=16940874

Hello,

the same happend here with one WU (wu_Qsqrt421_DS3x8_CV1_S815_N2_-194161_N1_805984_k2_-1).

Its running more then seven days now. Since Yesterday evening it shows "time to complete: 00:00:00".

Only used time is counting up. What to do? Wait or Abort it?
Several other work units with more than 5 or 6 days were successfully completed before.

(Sorry for my very bad english...)

O.K., no answer ...

So I'll kill this bloody WU after arrival at home this evening.

Ouch ... assuming no answer after less than 5 hours... with two postings only.

Do you think everybody here is only waiting for the unbelieveable asset to help YOU ... I mean because it's YOU?! Day and night? Around the world?! You should think about this!

Let the WU run, I've seen this before for days on multiple machines. That's quite normal (good looking or not) and the WU will finish.

O.K., no answer ...

So I'll kill this bloody WU after arrival at home this evening.

People do need to sleep sometimes...

But to answer your question, the WU will eventually finish. The problem is the progress meter is not being reported correctly to the client. I uploaded a fix for this 2 days ago, which you may not have picked up yet. The latest version of the app is 2.10.

I uploaded a fix for this 2 days ago, which you may not have picked up yet. The latest version of the app is 2.10.

Correct. He picked up WU 15561275 on 9 April, with application v2.08

So it'll be showing as deadline expired on his local machine, which may account for some of his impatience - but the server isn't expecting it back until 26 April.

I uploaded a fix for this 2 days ago, which you may not have picked up yet. The latest version of the app is 2.10.

Correct. He picked up WU 15561275 on 9 April, with application v2.08

So it'll be showing as deadline expired on his local machine, which may account for some of his impatience - but the server isn't expecting it back until 26 April.

It will take somedays to complete all units running under application 2.08. I have 11 on my notebook and some units on my server.

Hi, ist me again,

I just aborted this work unit after 7 days 14 hours.

Link: http://numberfields.asu.edu/NumberFields/result.php?resultid=16717548

May be I'm a little bit unpatient, but in future I will abort each work unit running three days or longer. For me it seems to be right.

(O.K., I didn't keep in mind that the project is located in Arizona, just the other side of earth... I'm really sorry)

I think you should change the project. What you've done and announced to do is only a great waste of computing time and electric energy. Why did I answer you?

Sorry, but this much ignorance after your whining because nobody answered after 10 seconds makes me angry. Get lost!

You are the greatest .... :-)) That was really helpfull now.

Here to talk with You, that might be wasting energy. Bye my friend...

Hi, only to close this unpleasant topic of Yesterday finally - there is a little stats of my last 14 days crunching:

last 14 days I finished successfully
249 work units (with about 254,000 Credits retourned), including:

9 WU running longer than 1 day +
3 WU running longer than 2 days +
3 WU running longer than 5 days

I'm still believing it was the right way to abort this one work unit, that was blocking one cpu core for a long time. There was no progress any more.
Now its running smoothly again - as it should run.

The only question that remains is:
Who thinks "Dj Ninja", who he is that he can determine whether I am allowed to support this project or not? Does he believe to be an admin ore developper or website owner or what ever? Okay - however, I will continue.

As the official admin for the site, it's my responsibility to remind everyone to "play nice". Now let's all get back to crunching...

Guys, stay calm.
Anyone is doing a great job here. We know that some tasks are running extremly long, even more that 1000´s of hours are possible on Qsqrt tasks.
I think it shouldn´t be a problem to gain some points for your "wasted" computing time.
@Eric No problem, isn´t it?


BTW:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x000007fefdac3a82

Engaging BOINC Windows Runtime Debugger...

@Richard and Eric

Can you give me information about this, please?

Task: http://numberfields.asu.edu/NumberFields/result.php?resultid=16717548

This was explained to me once, many years ago - by Rom Walton, I think.

The action was

Exit status	203 (0xcb) EXIT_ABORTED_VIA_GUI

- user clicked the abort button.

They (the BOINC developers) deliberately coded it to throw a breakpoint on abort, to get some state debug information and feed it back to the developer. Perhaps, like in this thread, the user aborted it because it seemed to be in an infinite loop? If so, we'd like to know which code segment had the bug so it could be fixed.

There aren't many developer aids in the standard BOINC client: why they chose this one, I don't know. Maybe there were a lot of infinite loops in their test code?