These say they are for GPU but have so far spent over an hour just running on a CPU thread.

Will they use the GPU ?

Hm, looks there may be an off-by-one error in our GPU code. We're enabling GPU0 but the script inside Blender indexes the GPUs from 1 for some reason. I will have to look into this to figure out what is going on and what has changed.

Switching back to CPU rendering for the remainder of this session and until a new GPU client can be released.

Okay, thanks.

How long do you think they will take on a single thread ?

Using this session to slowly and carefully run a few more GPU tests:
1) The code for GPU indexing has been updated to match the most recent changes in how Cycles uses GPUs
2) Preliminary test of OpenCL support for AMD GPUs
3) Test of configuring client binaries across multiple platforms inside BOINC using just one set of files

The 5.14 version still used the CPU.

Edit: I did go to check if the GPU had fired up but it had just completed !

New ones are using the GPU :)

Great to hear!

There's still some CPU used during the start-up and up to 1 full thread for managing the GPU.

Thanks, it's been a while since I had GPU work I couldn't remember how much got used !

The OpenCL test WU that was sent out for this session didn't seem to succeed at all. No reply was received from any of the machines that received it.
It will take a little while longer for the WUs to time out and hopefully, by then, some logs will show what the problem is.

Unfortunately I don't personally have modern enough OpenCL hardware available for testing yet.

I didn't get any of them. It also seems strange that no-one has returned anything (good or bad), as though they aren't making it to the client.

Will keep trying...