Well the only thing that appears you can do would not be to suspend tasks. Just suspend network activity to not get new tasks until you need to do so.

The econd run Leishmaniasis has finished. The current status
"inconclusive" so probaly that will be an invaid as well.

I feel there is something wrong with this new project.

NT

As eluded at top of this thread (I did ask about the CPU make), there are a few AMD's that somehow seem to produce a non-matching result [many AMDs do]. Via the initial 'Inconclusive' path these results end up declared invalid. If this repeats, suggest to de-select DSFL for that device until a solution is found.

Recently again a comment arrived about a certain P3 having a specific result error and when I looked it up, their average contribution to WCG overall was like 2.34 credit per day (16 points average). Got very low hopes, none really, that the programmers would go out to fix a bug and risk to break the software. These devices need to be considered for focus on sciences they can do without fail or be retired. In the not to distant future, the distributor will look at a device science specific history and automatically stop sending these if always / frequent invalid with a red line being printed in the message log of the client, possibly an individualized notice that stays in view for 30 days on the 6.12 and higher clients (email not probable).

--//--

hmmm, was ready something about an Ubuntu kernel bug. Done 500 or so on Natty, without fail. Getting into VM spheres and you'd want to get involved in BOINC 6.13 testing or the 6.12.38/39 Beta clients. Such esoteric environments are hard to catch and even harder to debug for the techs.

--//--

I had 60 DSFL WU and all turned into Inconcusive :-(
Very sad.
It is Intel CPU.
Wouldn't be possible to adjust validator to accept these results? Just an idea.