Bug reports for Ralph 5.20

Message boards : RALPH@home bug list : Bug reports for Ralph 5.20

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 1776 - Posted: 5 Jun 2006, 20:27:10 UTC - in response to Message 1764.  
Last modified: 6 Jun 2006, 20:47:12 UTC

You could have saved us some investigation if you would have told us. Anyway it's good to know that the reason is known and won't delay any further development.


It wasn't intentional. We posted as soon as we found the cause.

edit: actually I think it was intentional to help diagnose issues with the watchdog. I think it was taking a bit longer than expected and has since been fixed by Rhiju and Rom.

ID: 1776 · Report as offensive    Reply Quote
Profile dekim
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 20 Jan 06
Posts: 250
Credit: 543,579
RAC: 0
Message 1789 - Posted: 6 Jun 2006, 20:48:01 UTC - in response to Message 1763.  

Rom tells me it is waiting for the watchdog to finish for debugging. edit: to debug the watchdog.

Here is his response:

"When I added code .... to wait until
the thread is finished, it stalls for up to 30 minutes waiting until
watchdog makes its next check."

I think the watchdog can take up to 2x the cpu run time pref, which may explain the longer stalls.


ID: 1789 · Report as offensive    Reply Quote
Previous · 1 · 2

Message boards : RALPH@home bug list : Bug reports for Ralph 5.20



©2024 University of Washington
http://www.bakerlab.org