After reading some old BOINC logs of mine, I find some useful messages missing in newer versions of BOINC.

Since 5.8.x we have two times "starting task" (I still don't see any sense in that), "resuming task", "restarting task" and "computation finished". But while switching from one task to another one, there used to be the following message:

2006-09-12 15:52:03 [SETI@home Beta Test] Pausing task 01my06aa.17871.305.972158.3.126_0 (left in memory)

Next examples:

2006-10-18 09:44:06 [---] Using earliest-deadline-first scheduling because computer is overcommitted.

2006-10-18 09:44:06 [---] Suspending work fetch because computer is overcommitted.

2006-10-18 12:46:24 [---] Resuming round-robin CPU scheduling.

2006-11-25 18:03:15 [---] Allowing work fetch again.

OK, the EDF scheduling has become more complicated with 5.8.x, but it would be great, if there was at least a message when work fetch is suspended/allowed.

And last but not least (and -unfortunately- NOT missing ;)) something about the error messages. I think it was in some of the 5.8 versions... Error messages where easy to see, as they were displayed in red. Now you might not see some error messages, because all messages are black. :|

After reading some old BOINC logs of mine, I find some useful messages missing in newer versions of BOINC.

Since 5.8.x we have two times "starting task" (I still don't see any sense in that), "resuming task", "restarting task" and "computation finished". But while switching from one task to another one, there used to be the following message:

2006-09-12 15:52:03 [SETI@home Beta Test] Pausing task 01my06aa.17871.305.972158.3.126_0 (left in memory)

You have to have cpu_sched turned on in a cc_config file.

Next examples:

2006-10-18 09:44:06 [---] Using earliest-deadline-first scheduling because computer is overcommitted.

2006-10-18 09:44:06 [---] Suspending work fetch because computer is overcommitted.

2006-10-18 12:46:24 [---] Resuming round-robin CPU scheduling.

2006-11-25 18:03:15 [---] Allowing work fetch again.

OK, the EDF scheduling has become more complicated with 5.8.x, but it would be great, if there was at least a message when work fetch is suspended/allowed.

They just added in a new message for this in 5.10.16. "High Priority", IIRC. I don't have a log example though.

And last but not least (and -unfortunately- NOT missing ;)) something about the error messages. I think it was in some of the 5.8 versions... Error messages where easy to see, as they were displayed in red. Now you might not see some error messages, because all messages are black. :|

Yeah. I'd like to see this come back as well. I think there might be a few messages still displayed in red, but I'm not 100% certain on it.

---

Kathryn :o)

They just added in a new message for this in 5.10.16. "High Priority", IIRC. I don't have a log example though.

Don't go look for it, there is none.
It shows as Running, high priority in the Tasks tab only.

[error] messages are displayed in red.

---

Error messages or still displayed in red. They are no longer displaying 'informational' messages in red as this was freaking out people who didn't realize they weren't error as such.

They just added in a new message for this in 5.10.16. "High Priority", IIRC. I don't have a log example though.

Don't go look for it, there is none.
It shows as Running, high priority in the Tasks tab only.

[error] messages are displayed in red.

Enabling cpu_sched_debug will out output:
{project} [cpu_sched_debug] Result R projected to meet deadline.
{project} [cpu_sched_debug] Result R projected to miss deadline.
{project} [cpu_sched_debug] Project has 1 projected deadline misses