Apologies. There was an issue with how the job was setup, which resulted in many computational errors. The job was suspended while we fix the problems.

I see we have new tasks to crunch, and they are still requiring up to 6gb per task. Insanity. I thought this was going to be fixed?

One of our scientists is trying to submit a job with a couple of problems. We have decided to move his task to a resource with higher computing power. Unfortunately, this will probably mean that volunteers will not have a job to crunch on.

Would not be easier to change project settings to stop feeding WUs to users with not enough RAM?

That's too bad. This morning we moved the Pypy to our own set of dedicated resources.