This is not a bug, per se, but I sure wish the implementers would UNdo the fact that the "Starting Task" message seems to be no more in 7.4.42. It makes it much more difficult to see when I ran out of CUDA tasks now, like in the outage today. I basically have no way of knowing which tasks are CPU and which are GPU, since BOINC no longer tells me which slot a task is started in, and if it is CUDA or not....

Can you please rewind this particular change? Pretty please?

---

I'm not exactly sure what you are talking about, but I do know ...

If you suspend a task, and it resumes work, there is no message in BOINC that it started again. You just see it in the tsk list.

---

I'm using BOINC v7.4.42. I still have Starting task in my event log (of course you haven't specified where you were seeing this, so I'm assuming it was in the event log).

5/17/2015 5:26:04 PM | SETI@home | Computation for task 09dc12ab.9739.10853.438086664195.12.37_1 finished
5/17/2015 5:26:04 PM | SETI@home | Starting task 03ja13ai.1338.12746.438086664204.12.240_0
5/17/2015 5:26:06 PM | SETI@home | Started upload of 09dc12ab.9739.10853.438086664195.12.37_1_0
5/17/2015 5:26:14 PM | SETI@home | Finished upload of 09dc12ab.9739.10853.438086664195.12.37_1_0

And if you want to see how many tasks you have for a resource, you can always use the Tasks tab in BOINC Manager, then Show All Tasks, then look in the application column to see what application that workunit is going to be crunched with. The application should tell you whether it is CPU or GPU.

As Hal says, the information you need is available at a glance on the tasks tab - though you may need to make the 'Application' column wider to see which tasks are on the GPU. The slot number is available via 'Properties'.

But what jravin wants to see is

18/05/2015 07:47:09 | SETI@home | [cpu_sched] Starting task 09oc12ad.10229.263082.438086664208.12.89_0 using setiathome_v7 version 700 (cuda42) in slot 3

and it's still there in v7.4.42

You just need to use the handy 'Event log options' dialog



and select 'cpu_sched', as I have done.

Richard - thank you, I hadn't known that dialogue existed. Was it mentioned anywhere when I installed 7.4.42? If it was, I never saw it.

Others - yes, I know about the Tasks list - but the info goes away when the tasks cycle through. I need it in the Event Log to know when (for example) my last CUDA task finished during Tuesday maintenance, so I know how long my GPUs were idle. (If they were).

---