I'm severely tempted to stop crunching until this gets resolved.....

Any ideas?
It looks like the wing men also completed validation with no credit.

For information: this has already been raised in the News/Admin Updates Discussion thread and Kevin acknowledged it...

I've had a look through my results currently listed as valid (ignoring the large number of Separation orphans that are still listed!) and made a post about it in that thread; it may or may not be of interest... (It's quite long, so I've not re-posted it here.)

For what it's worth, I haven't [yet] seen any of these tasks that also have a validated wingman with no credit, so I can't see if the possible explanation for zero credit still holds if verification should have been possible; I'll have another look in a day or two to see if that changes, as I'd be interested to see one or more such WUs to have a look :-)

Cheers - Al.

I do not use a config file and enabled N-body in Milkyway Preferences. I limit CPU use to 2 cores (such as 42% of the CPUs in a 6 core system) and measure temperature using Mooo System Monitor. So the Milkyway tasks use 2 CPUs.

Some N-body tasks take less than an hour, while others a few hours. When a task has used more than a few days of Elapsed time, it is correct to abort it?

FYI: I have a Windows OS and an Intel Core 5 CPU 9th gen. about 6 years old. I check the task manager for CPU use.

Any tips or suggestions?

At first i have read buster as booster,

Why did we not just stop releasing tasks first and THEN shut down the project, so a whole bunch of work doesn't get stuck in pending validation?
Can we at least get points for the work even though the results are worthless?

And what I'm assuming is "a lot" of electricity required to power the GPUs to do work that will have no scientific value.
Only 2 more days but still very wasteful.

But still probably ALOT less wasteful than all those CEO's etc flying to Switzerland on their private jets to attend a conference on 'saving energy'.