Thread 'ALERT: elapsed time bug in Boinc 6.12.34 (x86)'

Message boards : Questions and problems : ALERT: elapsed time bug in Boinc 6.12.34 (x86)
Message board moderation

To post messages, you must log in.

AuthorMessage
nuninho1980

Send message
Joined: 15 Apr 12
Posts: 4
Portugal
Message 43518 - Posted: 15 Apr 2012, 14:16:52 UTC

Welcome to Boinc! :)

I have XP x86 SP3 and this version of Boinc.

I read the elapsed time "01:25:30" and I quitted this program. I ran again and read "01:21:00"!?? It's earlier!?! But bug. :O lol!

Please you should fix elapsed time issue... ;)
ID: 43518 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15634
Netherlands
Message 43521 - Posted: 15 Apr 2012, 16:51:46 UTC - in response to Message 43518.  

6.12 is no longer being updated. BOINC 7.0 is the latest version.
ID: 43521 · Report as offensive
nuninho1980

Send message
Joined: 15 Apr 12
Posts: 4
Portugal
Message 43522 - Posted: 15 Apr 2012, 19:05:37 UTC

Ok. :) I tried to update to 7.0.25 x86. I read elapsed time "02:54:00" while this program takes half minute and I quitted program. I tried to run again it but I got still earlier ("02:53:00")!?! Earlier is bad.

Please... ;)
ID: 43522 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15634
Netherlands
Message 43523 - Posted: 15 Apr 2012, 20:12:19 UTC

What project is this for?
Which application of that project?
Does the application checkpoint, aka write its state to disk?
If it does, does it follow the computing preference of "Tasks checkpoint to disk at most every X seconds"?

When an application checkpoints, as said it writes the state of where it is in the task to disk. When you quit BOINC before a next checkpoint could be made, the earlier checkpoint will be used when you continue. This shows as your 'bug', which isn't a bug. It just restarts from the earlier point in time as is noted in the checkpoint file in the tasks slot directory.
ID: 43523 · Report as offensive
nuninho1980

Send message
Joined: 15 Apr 12
Posts: 4
Portugal
Message 43525 - Posted: 15 Apr 2012, 20:42:54 UTC
Last modified: 15 Apr 2012, 20:43:50 UTC

Project is "PrimeGrid"

2 applications of this project are "Genefer (World Record) 1.07 (cuda32_13)" and "Cullen/Woodall (Sieve) 1.01" - its are bug.

But other applications aren't bug. :)


My PC specs:
CPU: AMD Phenom II X6 1055T@stock
GPU: eVGA GeForce GTX 480@reference+@stock :D
ID: 43525 · Report as offensive
ProfileJord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15634
Netherlands
Message 43533 - Posted: 16 Apr 2012, 5:24:37 UTC - in response to Message 43525.  

As I said, checkpointing will write its state of that point in time to disk. There is no real time checkpointing, where the application writes its state to disk every second of the task. So whenever you exit BOINC & restart later, it'll start from an earlier point in time, as that's what is written in the checkpoint file.

And even if you wanted it fixed, you'd have to go to Primegrid and ask the application's developer about it, as it's his application that does this checkpointing. BOINC only shows what the application reports, perceived right or wrong.
ID: 43533 · Report as offensive
nuninho1980

Send message
Joined: 15 Apr 12
Posts: 4
Portugal
Message 43545 - Posted: 16 Apr 2012, 13:53:49 UTC

I already posted in forum "PrimeGrid" but I hope the issue fixed for program Boinc or application... Thank! ;)
ID: 43545 · Report as offensive

Message boards : Questions and problems : ALERT: elapsed time bug in Boinc 6.12.34 (x86)

Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.