One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

Maybe?
I've got a sebv1 Task that finished in 3 hours. There's a sebv2 Task that is running, and is looking at 10.5 or so to complete- my sebv2 Tasks that have completed have taken 10hrs 45min (2 of them), 4hrs 20min and 5hrs 40min.

---

Grant
Darwin NT

There's a sebv2 Task that is running, and is looking at 10.5 or so to complete

Now looking at 13hrs 15min to completion.

---

Grant
Darwin NT

One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

It finally finished successfully, before it reached 23 hours. I suspect that the sebv2 tasks need much larger time estimates,

I've got a sebv2 task that has come to a near standstill since reaching 99.55% about 20 hours ago. It is now at 99.603%, elapsed time of 1d 21:49:00 and has progressed 0.003% in 45 minutes but has not progressed for the last 15 minutes. The time remaining keeps recalculating to 00:10:55 +- 01 second, adjusting between 00:10:54 and 00:10:57 for hours. I've seen it work down to --:--:-- then, eventually, recalculating to 00:10:55. The deadline is in about 5 hours so I'm just going to let it run and see what happens. Oops!! Just made 0.001% progress after 20 minutes!

All the other Rosetta task running are not sebv2 and are making consistent progress.

---

I've got a sebv2 task that has come to a near standstill since reaching 99.55% about 20 hours ago. It is now at 99.603%, elapsed time of 1d 21:49:00 and has progressed 0.003% in 45 minutes but has not progressed for the last 15 minutes. The time remaining keeps recalculating to 00:10:55 +- 01 second, adjusting between 00:10:54 and 00:10:57 for hours. I've seen it work down to --:--:-- then, eventually, recalculating to 00:10:55. The deadline is in about 5 hours so I'm just going to let it run and see what happens. Oops!! Just made 0.001% progress after 20 minutes!

All the other Rosetta task running are not sebv2 and are making consistent progress.

The timer and percentage figures are typical of a task that’s overrunning its estimate (because the software has no idea how much it will overrun by) and I believe that the sebv2 tasks have been doing that fairly consistently.

The good news is that it will just go to completion suddenly, the bad news is that no-one can tell when.

Server needs a kick - no tasks coming down

Program	        Host	Status
transitioner1	bwsrv1	Not Running

Application	Unsent	In progress
Rosetta	        5	480390

---

and no validation too

https://munin.kiska.pw/munin/rosetta-day.html

Server Status page shows the Transitioners are down. Someone needs to give things a nudge.

Tasks ready to send          1
Transitioner backlog (hours) 8.98    (usually zero, or very close to it).

---

Grant
Darwin NT

Server Status page shows the Transitioners are down. Someone needs to give things a nudge.

Just when I reattach a Ryzen 3900X, things fall apart. Back to OPN.

---

and no validation too

https://munin.kiska.pw/munin/rosetta-day.html

No indication of that on the server page, but you're right - several here still waiting after @6hrs

---

Always wondered what a transitioner did.

Always wondered what a transitioner did.

A lot.


From the Seti@home website server page.

transitioner: Handles state transitions of workunits and results. Basically, the transitioners keep track of the results in progress and makes sure they properly move down the pipeline. It is always asking the questions: Is this workunit ready to send out? Has this result been received yet? Is this a valid result? Can we delete it now?

Basically it moves the Task from one state to another. Ready to send, sent & awaiting on a result, result received- Is the result Valid? If so, move it to the science database & delete it after a set time period. If not, send out another copy, then check it's result. Has it timed out? Send another one.

---

Grant
Darwin NT

I see the Scheduler on bwsrv1 has gone AWOL now. I hope it sends us a postcard.

Looks like none of you bothered to look at a weather report for Seattle, WA, USA.

I did, and found that today's weather includes times above freezing and times below, with snow expected.

That means a lot of ice on paths to and from the building with the server, so delays fixing any problems are likely.

Looks like none of you bothered to look at a weather report for Seattle, WA, USA.

I did, and found that today's weather includes times above freezing and times below, with snow expected.

That means a lot of ice on paths to and from the building with the server, so delays fixing any problems are likely.

That's why remote management is such a wonderful thing,

And it looks like they were successful. "Project is down for maintenance" is what i got when i first checked in this morning, but now the web site is back up & work is flowing again.
Thanks to whoever it was that got it working again.

---

Grant
Darwin NT

Two tasks downloaded on my fairphone2 Under the tasks view they both say download complete 0.000%

BOINC version is 7.16.16 from the BOINC site as I understand this version not available from Google Play.

Two tasks downloaded on my fairphone2 Under the tasks view they both say download complete 0.000%

BOINC version is 7.16.16 from the BOINC site as I understand this version not available from Google Play.

"David Anderson:
Version 7.16.16 of the BOINC Android client has been released. This is the first new Android version in over 4 years, and is a major rewrite of the GUI. Thanks for Vitalii Koshura, Tal Regev, and Isira Seneviratne for their work on this.

The new version is available from the BOINC web site and (for Amazon Fire tablets) from the Amazon app store. It's not on the Google play store because of new restrictions imposed by Google; hopefully this will be resolved in a future version."

I personally don't update every time a new update gets released, I let other try it out and figure out how it actually works and list the things it does differently, then if I either don't care about the new things or like them I will update. Some times though the older versions just work differently enough to make me keep them.

Another reason not to update right away is the Projects need to implement any necessary compatibility changes too. Some Projects are waaaay behind in their version of the Boinc Server side software.

I have two failed work units in the last batch. One also failed again with another user's attempt on the same platform (windows_x86_64)

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1197364660

However this one failed on windows_x86_64 but succeeded on aarch64-unknown-linux-gnu

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1197364006

Are these types of asymmetrical failures indicate platform bugs vs tasks which fail on all platforms?

---

Are these types of asymmetrical failures indicate platform bugs vs tasks which fail on all platforms?

Sometimes/maybe.
If the Tasks only ever fail & only ever complete on particular platform, then you can put it down to the application. But due to the fact that when a Task is run it is started with a random seed value, so even if you were to run the same task 50 times on the very same system, it may error out on some occasions and not others, all due to the different initial value used.

---

Grant
Darwin NT