Author Message

Sergei Chernykh



Project developer

Project administratorProject developer Send message

Joined: 5 Jan 17

Posts: 445

Credit: 72,451,573

RAC: 0

Joined: 5 Jan 17Posts: 445Credit: 72,451,573RAC: 0 Message 779 - Posted: 27 Mar 2018, 17:45:25 UTC

Last modified: 27 Mar 2018, 18:56:15 UTC

Unfortunately, it skipped some numbers in an unpredictable way for "large primes" work units for the last 20 days 9 days. I'll have to reissue all such work units to cover everything missed. The GPU versions for all platforms are already updated.



Sorry for the mess, but it's good that the bug is fixed relatively early, because it was hard to notice. There was a serious bug in GPU version: https://github.com/SChernykh/Amicable/commit/3470ed855d244100f37b0b7ab4c912d2b9365a93 Unfortunately, it skipped some numbers in an unpredictable way for "large primes" work units for the last9 days. I'll have to reissue all such work units to cover everything missed. The GPU versions for all platforms are already updated.Sorry for the mess, but it's good that the bug is fixed relatively early, because it was hard to notice. Reply Quote ID: 779 · Rating: 0 · rate:

Kellen

Send message

Joined: 14 Nov 17

Posts: 70

Credit: 1,000,005,236

RAC: 0

Joined: 14 Nov 17Posts: 70Credit: 1,000,005,236RAC: 0 Message 780 - Posted: 27 Mar 2018, 18:13:12 UTC - in response to Message 779. Well, I'm glad this was caught early! 20 days is a lot better than 200 days :)



Is this bug the reason for the semi-random work unit runtimes lately? Reply Quote ID: 780 · Rating: 0 · rate:

Sergei Chernykh



Project developer

Project administratorProject developer Send message

Joined: 5 Jan 17

Posts: 445

Credit: 72,451,573

RAC: 0

Joined: 5 Jan 17Posts: 445Credit: 72,451,573RAC: 0 Message 781 - Posted: 27 Mar 2018, 18:48:44 UTC - in response to Message 780. Is this bug the reason for the semi-random work unit runtimes lately?

Yes, it was running random percentage of a work unit instead of full 100%. Yes, it was running random percentage of a work unit instead of full 100%. Reply Quote ID: 781 · Rating: 0 · rate:

Sergei Chernykh



Project developer

Project administratorProject developer Send message

Joined: 5 Jan 17

Posts: 445

Credit: 72,451,573

RAC: 0

Joined: 5 Jan 17Posts: 445Credit: 72,451,573RAC: 0 Message 782 - Posted: 27 Mar 2018, 18:54:36 UTC

Last modified: 27 Mar 2018, 19:00:48 UTC Good news: I was able to narrow down the invalid work units range to only last 9 days after further analysis of this bug. Reply Quote ID: 782 · Rating: 0 · rate:

Speedy

Send message

Joined: 6 Jun 17

Posts: 31

Credit: 40,733,803

RAC: 26,132

Joined: 6 Jun 17Posts: 31Credit: 40,733,803RAC: 26,132 Message 826 - Posted: 7 May 2018, 23:20:01 UTC - in response to Message 782. Good news: I was able to narrow down the invalid work units range to only last 9 days after further analysis of this bug.

This is great news. Is there a way to tell if we are running old work units or have we caught up with processing old work? This is great news. Is there a way to tell if we are running old work units or have we caught up with processing old work? Reply Quote ID: 826 · Rating: 0 · rate:

Speedy

Send message

Joined: 6 Jun 17

Posts: 31

Credit: 40,733,803

RAC: 26,132

Joined: 6 Jun 17Posts: 31Credit: 40,733,803RAC: 26,132 Message 828 - Posted: 8 May 2018, 5:32:35 UTC - in response to Message 827. We caught up more than a month ago, it's all new work now.

So we did pleased to hear that you got all the results you needed rechecked So we did pleased to hear that you got all the results you needed rechecked Reply Quote ID: 828 · Rating: 0 · rate: