I successfully completed one of these units.

http://www.gpugrid.net/workunit.php?wuid=5228104

3 Mar 2014 | 22:14:10 UTC 3 Mar 2014 | 23:07:04 UTC Completed and validated 1,477.65 1,359.77 9.02 CPU only app v1.04

Two others are still running on my other machine.

Why are we bothering with CPU work units? They are so much slower than GPU WU.

v1.07 finally completed on my android without failing. Woohoo.

Folding@home at Stanford just rolled out a really nifty Chrome app which just chugs along using CPU power. So easy to use!

v1.07 finally completed on my android without failing. Woohoo.

Just started a CPU only app 1.04 on a Windows 7 box with BOINC 7.2.37. After the job ran for about a minute, the progress column now says "1.#IO%" and the Remaining column says " ---" (instead of showing hh:mm:ss).

Also running a CPU only app 1.01 on a Linux Ubuntu 13.10 box. After 6 minutes, it shows that progress is 18302.850%. Remaining says " ---". Job completed after ~10 minutes and shows that it is "Completed and Validated".

Let me know if you need more info.
captainjack

I'm not sure what the expected run times are, but the tasks I've completed have run between about 5000-6500 seconds.

Observations for my hosts (Win7-64, 3 Intel, 1 AMD):

1) Many tasks still running long after progress has reached 100%. WU properties show nonsensical values for the fraction done.
2) When suspended then resumed, those tasks finished shortly after starting to run again*
3) I've seen progress values in a wide range between 0%-100%. Often, WU properties fraction done does not match progress value.

*[edit]Except when they don't finish shortly after restarting.[/edit]
____________

In addition to observing the same behaviors others have already posted ...
I just attached a Win7 x64 client that does not have an NVidia card and while the server status says there are no CPU tasks available the event log message doesn't match ... says no "long" tasks available?

3/4/2014 10:04:45 PM | GPUGRID | update requested by user
3/4/2014 10:04:48 PM | GPUGRID | Sending scheduler request: Requested by user.
3/4/2014 10:04:48 PM | GPUGRID | Requesting new tasks for CPU
3/4/2014 10:04:50 PM | GPUGRID | Scheduler request completed: got 0 new tasks
3/4/2014 10:04:50 PM | GPUGRID | No tasks sent
3/4/2014 10:04:50 PM | GPUGRID | No tasks are available for Long runs (8-12 hours on fastest card)
____________
Thanks - Steve

Look in your preferences. You have it set somewhere to only do Long runs and not do the cpu tasks.

Thanks for the help guys.

Probably the progress info is not working.

How many CPU jobs do you get per CPU core?

gdf

Thanks for the help guys.

Probably the progress info is not working.

How many CPU jobs do you get per CPU core?

gdf

I have added two devices to gpugrid two days ago; have not got a single wu ...

These are pathfinder WUs for a new project that we are currently scoping. Please keep crunching them, it's giving us useful information. More details on the project soon!

Matt

You can already run them on an Android device.

I see GPUgrid in the list of projects now in the BOINC app, but it says 'device not supported' and doesn't seem to be downloading work once I add the project. I have a Galaxy S4 phone.

I successfully run one of these units several days ago. Today, three of them have failed with the same "segment violation" error, they all in Linux in the same PC.

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
# (BOINC) Mapping [ligand.db]->[ligand.db]
# (BOINC) Mapping [result.db]->[../../projects/www.gpugrid.net/T2-TONI_DBTEST1-0-1-RND0994_0_0]
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt]
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt]
SIGSEGV: segmentation violation
Stack trace (7 frames):
[0x4932ad]
[0x5242b0]
[0x4a4f61]
[0x4a3a1c]
[0x40a8eb]
[0x525aeb]
[0x400449]

Exiting...

</stderr_txt>
]]>