Dear Team, (Translate with Deepl.com)
since a few days the tasks are "extrapolated".
Instead of the remaining time decreasing, it is getting longer and longer.

After a restart it goes for a few hours again and then it starts all over again .-(

Meanwhile 4 days calculated and remaining time over 6 days. Increasing.

What is going wrong here?

Greetings Rainer

edit

just found out: it is enough to pause the tasks in the Boinc manager and then go back to always run.
But of course this is not a state.
I have a few computers and can use my time better....
Greetings, Rainer

Hello! Some workunits really can be very long due to properties of compounds and their distribution into packages. For example, on my Ryzen, for one of unusual task, one of compound has been processed in 111 seconds, but next - in 2338 seconds. If task include more "long" compounds than usual, it's getting long.
Also, time that need for modeling of compound and target docking varies from target to target.

If you see an unusual task, simply check property "CPU time since last checkpoint" in BOINC Manager. If you see hours on computer with "Ryzen-class" CPU - you can check time of last change (or contents) of file docking_out.log in task slot directory. If it changes - computing is fine.

P.S. I also see on my computer, that tasks in last 2 days become longer. Don't panic, that is normal. :)

Moin, (Translate Deepl.com)

no The objection does not fit my contribution:
We are talking past each other.

I do not speak about long running times in itself, but that the remaining time >drastisch< strongly rises!
Last time the remaining time showed > 420 days and jumped further.

I calculate for Boinc since 2006 and know about the possible long runtimes.
Greetings, Rainer

... I do not speak about long running times in itself, but that the remaining time >drastisch< strongly rises!
Last time the remaining time showed > 420 days and jumped further. ...

Yes, predicted time like this is abnormal. Would you post some info about computer (or host id) and one of two strange tasks: elapsed time; estimate time; contents of "docking_out.log" from slot directory; time of last change of "docking_out.log" and current time.

Thank you!

Sorry, deepl.com as Translate is down.
Mi englich is very wrong.

my ID-Computer is 41159, 41160 etc..
all WU cancelt, no Info
My Hardware: Ryzen3700x with 32GB Ram, stock, no OC
1700 32GB stock
an any Hardware.
docking_out.log is 0 Byte
Greets Rainer

I looked data about tasks, computed by your hosts. Successful tasks were completed in the usual time. If an anomaly really occurred, then I think it was necessary to restart BOINC or computer. You can also compare with my computer.

I have similar one task is 344 days and another 103 days to complete although their supposed to be completed by the 29th of this month? Is their an error in the WU's I wonder.

---

Hi! :)

I have similar one task is 344 days and another 103 days to complete although their supposed to be completed by the 29th of this month? Is their an error in the WU's I wonder.

How many time this task already consumed and what process reached?

I make it simple cancel the project, don't accept, project that prolong deadline, that mean they don't know what they are doing, and time slot windows is wrong and they forget pc can be use to other things,
and this is what happen then you micro-mangement thing and you have no knowledge in human behavior.
i'm sure ofc. you buy a pc and only run client , and you have no use of a pc to do other things.

ps
any WU longer then 24hour, over 3 days off line work only at sleep time, should start to raise a issue for normal user.

gl with it.
this project is shutdown by me as user, until they change WU time slot. window, and gl send msg to client so i open for traffic again, i will not bother read here or waster my pc resource on bad managment.

any pause or reboot or restart client will cause issue for even more prolong WU time, this is seen before in other screwup time index and lost save, nothing new in bonic manager lack of option.

C:\programdata\BOINC\slots\#\docking_log should display more correct estimated time for completion.

I have experienced similar issues. Usually a WU takes about 12 hours to complete. Some tasks not only take waaaay longer, but the completion % drops and the estimated completion time is completely inaccurate.

It's honestly put me off from running this projects, but I will give it another shot today.

C:\programdata\BOINC\slots\#\docking_log should display more correct estimated time for completion.

In some cases I have found the boinc client 7. 24. 1 to show a more realistic completion time than the log in the slot directory. This is on a Windows 11 pro

I have three , (possibly more...), jobs with a problem. All had run 1d+, and had been running normally. For a printer issue, I had to power the system down and up again. Upon doing so, I now see one has 169 days, one 232 days and the other 316 days, all rapidly increasing. I've suspended them for now. Others that were running appeared to start again, but watching them, the remaining time looks to be in a short cycle. I have suspended all but one of them also. If it doesn't change for a while, I'll suspend that also. It would seem you have an issue with tasks running when a power cycle is necessary...

That is several CPU days wasted. No new tasks set.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream...

There are a couple of known bugs in the CmDock science app:

• On Windows, BOINC doesn’t know about its checkpoints. After a restart, the percentage complete usually recovers after a few minutes, but the previous elapsed CPU time is lost and so the BOINC credit will be lower. The problem has been fixed at source, though the project hasn’t updated its application yet.
  
  
• If a task resumes from a checkpoint but gets restarted before it has saved another checkpoint, it might restart from the beginning or report completion and fail validation. (Also mentioned in threads here and here.) The bug has been reported.