Author |
Message |
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
I have 4 Cullen/Woodall Prime Search (Sieve) v1.00 units with error -177 (Maximum elapsed time exceeded).
The units are:
172783744
172434699
172430125
172429647
How to solve?
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
RytisVolunteer moderator Project administrator
 Send message
Joined: 22 Jun 05 Posts: 2653 ID: 1 Credit: 102,353,894 RAC: 84,727
                     
|
Version 1.00 has been pulled because it is running way too slow - we will release it once again when/if the problem is solved.
____________
|
|
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
Okay, but what's with the ~48hrs of computing time. I hope not lost.
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
I found 3 more GCW sieve v1.00 units with credits (resultid=172433465, resultid=172430509, resultid=172430206) and a 4th unit (resultid=172783799) is underway at 12.5hrs of ~15hrs.
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 261,913,874 RAC: 11,928
                            
|
Mea culpa! I didn't read all the instructions when compiling the app.
____________
|
|
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
Resultid=172783799 also errored out past 14hrs of crunching.
I have now lost 3 days of calculating time. :(((
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 261,913,874 RAC: 11,928
                            
|
The old 32-bit Windows GCW Sieve app I compiled is bad. You should stop using it. I think I have a fixed version, but you should abort all the old WUs.
____________
|
|
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
NNW, reported all units back and reset PG.
I don't understand, how other crunchers could do these jobs with the same faulty app...
[edit]
Will this wuid=117796620 calculated by another win32-cruncher with the same faulty app?
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
|
Greetings All
Have switched 1 duel core over to GCW Sieve. Windows 32 bit. (Amd 4200+ 1.5 GB ram) Will update when results are in.
Mike |
|
|
|
Greetings All
Have switched 1 duel core over to GCW Sieve. Windows 32 bit. (Amd 4200+ 1.5 GB ram) Will update when results are in.
Mike
Gcwsieve v1.01 6326113_36011740e6_36011800e6 23412.80 seconds.
Gcwsieve v1.01 6326106_36011320e6_36011380e6 23363.00 seconds.
Both marked as valid.
Mike |
|
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 261,913,874 RAC: 11,928
                            
|
The bad version of the app lacked optimizations for x86. That's why it was so slow. And it was failing only because it was slow; some insanely-overclocked people might have gotten work done in time.
I fixed the app, apparently it's been updated on the server, and it seems to be working better now.
____________
|
|
|