Message boards : Questions and problems : ALERT: elapsed time bug in Boinc 6.12.34 (x86)
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Apr 12 Posts: 4 ![]() |
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... ;) |
![]() Send message Joined: 29 Aug 05 Posts: 15634 ![]() |
6.12 is no longer being updated. BOINC 7.0 is the latest version. |
Send message Joined: 15 Apr 12 Posts: 4 ![]() |
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... ;) |
![]() Send message Joined: 29 Aug 05 Posts: 15634 ![]() |
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. |
Send message Joined: 15 Apr 12 Posts: 4 ![]() |
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 |
![]() Send message Joined: 29 Aug 05 Posts: 15634 ![]() |
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. |
Send message Joined: 15 Apr 12 Posts: 4 ![]() |
I already posted in forum "PrimeGrid" but I hope the issue fixed for program Boinc or application... Thank! ;) |
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.