I have recently reinstated Boinc on my Macbook Pro and am getting the above message occasionally. I'm running 7.8.4 which I had heard was supposed to address this message. I can't see what task is postponed or see any undesirable effect, things seem to be computing fine as far as I can tell. I did reboot this morning to see if that helped but it didn't seem to change anything.

---

--
Bill Waggoner

That will likely be a GPU app from SETI@Home - we had a spate of those recently.

Remind me to open an issue for the task, app, or project name to be included in the Event Log for cases like this.

You're probably right about the project name being listed (perhaps Bill can confirm, but I'm pretty sure that 'Suspicious pulse results' are only reported by SETI).

But what we're missing is precisely which 'Task' has been 'postponed': knowing the name would enable us to look up the stderr_txt on the project website (if the project's server code is new enough to have that search-box facility).

I'm running 7.8.4 which I had heard was supposed to address this message

I know where the confusion comes from: me.
At the time, in the Seti forums, I was helping a person called 'listener' with this problem, when I found that all Macs with BOINC 7.8.x with an AMD Compute Engine and High Sierra showed the memory on that CE in negative form. That's when I informed the developer of that and he released a new version of BOINC that fixed that, 7.8.4

Since the Task postponed: Suspicious pulse results message coincided with the release of a newer science application that caused the end of reports for Task postponed: CL file build failure, I thought that maybe these two were part of the same problem (the negative memory and the suspicious pulse results). Therefore I asked 'listener' to look if 7.8.4 fixed this problem. It did not. He still had that, intermittently.

However, these messages only show at times, but the tasks that have them seem to finish fine.
Although some do exit with the 'too many exits' error. That's the ones we need to look into, and know the application for.

---

Remind me to open an issue for the task, app, or project name to be included in the Event Log for cases like this.

For once BOINC development shines. Feature delivered in -3 months and you haven't even opened the issue yet!

:)

Lovely jubbly. Commit SHA or PR#, please, so I can see if it's been deployed yet?

#1978

Didn't make it to 7.8.

#1978

Didn't make it to 7.8.

Well, I tried. #2065