Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 89
Posts: 89   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 312907 times and has 88 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Thx for helping captainjack!

The only WU I procesed successfully yesterday is already validated. But I had a bunch of WUs that produced errors... Maybe that is the cause.


Here some details about the errors, hope that helps:

- Samsung Galaxy Note N7000, 2 cores, Android 4.1.2
- yesterday 10 Beta-Android WUs received (SN2S and FAAH), 1 Finished, 9 produced Errors

Here three exemplary result logs of WUs that produced errors (errors of the others were similar):

Result Name: BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 1327_ 0--
<core_client_version>7.2.4</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[21:49:43] Number of tasks = 5
[21:49:43] Starting task 0,CPU time is 0.000000.
[21:49:43] ./ZINC57531546.pdbqt size = 25 6 ../../projects/www.worldcommunitygrid.org/beta18.x4I7G_RT_NNRTIadj_wNNRTI.pdbqt size = 9714 0
Quit requested: Exiting
[22:04:57] Number of tasks = 5
[22:04:57] Starting task 0,CPU time is 0.000000.
[22:04:57] ./ZINC57531546.pdbqt size = 25 6 ../../projects/www.worldcommunitygrid.org/beta18.x4I7G_RT_NNRTIadj_wNNRTI.pdbqt size = 9714 0
ERROR: VINA was killed by signal 9.
Retrying task.
[22:05:50] Starting task 0,CPU time is 0.000000.
[22:05:50] ./ZINC57531546.pdbqt size = 25 6 ../../projects/www.worldcommunitygrid.org/beta18.x4I7G_RT_NNRTIadj_wNNRTI.pdbqt size = 9714 0
ERROR: VINA was killed by signal 9.
22:05:57 (27541): called boinc_finish

</stderr_txt>
]]>




Result Name: BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 0738_ 0--
<core_client_version>7.2.4</core_client_version>
<![CDATA[
<message>
process exited with code 239 (0xef, -17)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[21:10:14] Number of tasks = 7
[21:10:14] Starting task 0,CPU time is 0.000000.
[21:10:14] ./ZINC12979042.pdbqt size = 30 7 ../../projects/www.worldcommunitygrid.org/beta18.x4I7G_RT_NNRTIadj_wNNRTI.pdbqt size = 9714 0
ERROR: VINA was killed by signal 9.
Retrying task.
[21:48:21]:ERROR: Unable to open output file beta18.x4I7G_RT_NNRTIadj_wNNRTI_ZINC12979042_1524466264_out.pdbqt.
21:48:21 (14974): called boinc_finish

</stderr_txt>
]]>



Result Name: BETA_ SN2S_ AAB68717_ 0000027_ 3804_ 0--
<core_client_version>7.2.4</core_client_version>
<![CDATA[
<message>
process exited with code 239 (0xef, -17)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[20:45:44] Number of tasks = 16
[20:45:44] Starting task 0,CPU time is 0.000000.
[20:45:44] ./ZINC01119971.pdbqt size = 21 3 ../../projects/www.worldcommunitygrid.org/beta14.target_AAB68717.pdbqt size = 357 0
[21:01:27] Finished task #2147483391 cpu time used 628.150000
[21:01:27]:ERROR: Unable to open output file beta14.target_AAB68717_ZINC01119971_549370326_out.pdbqt.
21:01:27 (10973): called boinc_finish

</stderr_txt>
]]>

[Jul 14, 2013 3:28:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Ok, got some new WUs, just as the statistics update began. So I guess you were right captainjack, just that the day does not begin at 00:00 but with the statistics update ;)
Lets see if the tasks run correctly now. Or at least I will try to narrow the problem down.
[Jul 14, 2013 4:13:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
9maMSSuNWXgttyKdZhMemeXmEx8
Senior Cruncher
Puerto Rico
Joined: Feb 20, 2008
Post Count: 191
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Still testing on Android and all my workunits have been valid so far.
It takes 6 to 7 hours per task, which is good for an Android-powered smartphone.
----------------------------------------


[Jul 14, 2013 4:27:54 PM]   Link   Report threatening or abusive post: please login first  Go to top 
hunter1978
Advanced Cruncher
United States
Joined: Apr 24, 2010
Post Count: 109
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

6 or 7 results so far. Droid Razr Maxx. Working fine so far. Battery nice and cool.
----------------------------------------

[Jul 14, 2013 10:06:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
hunter1978
Advanced Cruncher
United States
Joined: Apr 24, 2010
Post Count: 109
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Too bad it doesn't work on an iPad. sad
----------------------------------------

[Jul 14, 2013 10:11:16 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Ian_UK
Senior Cruncher
England
Joined: Oct 15, 2006
Post Count: 153
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Temperatures and units fine with Galaxy S3. No errors (so far at least).

Not overly concerned, but elapsed times were significantly longer than had expected (up to 3* CPU time); might have something to do with running all 4 available cores. When quoting expected run times, as BOINC app only quotes elapsed time may be better to quote this with CPU time.

Originally thought would have to reduce number of cores crunched, to reduce power consumption as was discharging although thought was under charge (without BOINC it charged OK). Determined problem was with long power cable (2 connected together). Without extender cable had no issues.

With longest unit (BETA_ SN2S_ AAB68717_ 0000027_ 3002) at around 85% complete suddenly went down to one core from 4 processing; when selected Project Update the others restarted. Guess BOINC thought the core count had reduced. Nothing in log about it... Looked like BOINC had temporarily got confused (i.e. not unit issue).

Samsung Galaxy S LTE
boinc 7.2.4

BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 0274_ 0-- localhost Valid 13/07/13 15:10:14 14/07/13 17:48:37 3.59 / 11.89 14.4 / 13.2
BETA_ SN2S_ AAB68717_ 0000027_ 1337_ 1-- localhost Valid 13/07/13 15:10:13 14/07/13 22:21:31 4.72 / 15.42 15.5 / 14.7
BETA_ SN2S_ AAB68717_ 0000027_ 3002_ 0-- localhost Valid 13/07/13 10:37:16 14/07/13 20:14:44 6.62 / 19.48 26.1 / 20.8
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 1255_ 0-- localhost Valid 13/07/13 09:04:06 14/07/13 04:10:10 3.02 / 10.06 13.5 / 17.3
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 1237_ 0-- localhost Valid 13/07/13 09:04:06 14/07/13 11:42:36 3.83 / 13.87 19.2 / 12.1
BETA_ SN2S_ AAB68717_ 0000027_ 2092_ 0-- localhost Valid 13/07/13 09:04:06 14/07/13 07:13:40 3.86 / 13.77 18.4 / 19.5
BETA_ SN2S_ AAB68717_ 0000027_ 2015_ 0-- localhost Pending Validation 13/07/13 09:04:06 14/07/13 04:10:10 4.98 / 15.30 20.5 / 0.0
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 0448_ 1-- localhost Valid 13/07/13 01:28:09 13/07/13 22:02:41 3.62 / 10.01 13.4 / 11.9
BETA_ FAHV_ x4I7G_ RT_ NNRTIadj_ wNNRTI_ 0045262_ 0730_ 2-- localhost Valid 13/07/13 01:28:09 13/07/13 12:24:06 3.30 / 6.18 8.3 / 10.6
BETA_ SN2S_ AAB68717_ 0000027_ 4393_ 0-- localhost Valid 13/07/13 01:28:09 13/07/13 15:10:13 3.77 / 7.74 10.4 / 21.8
BETA_ SN2S_ AAB68717_ 0000027_ 0880_ 0-- localhost Pending Validation 13/07/13 01:27:43 13/07/13 10:14:32 3.73 / 8.46 11.3 / 0.0
----------------------------------------
[Jul 14, 2013 11:57:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

My phone (HTC Evo 3D) still consistently reverts to using one core, or only detects one core, or removes the 'number of cores' to use option. When I restart the phone it detects both cores and some time later defaults to 1. I think its when its talking to the WCG server and the settings are conflicting, it's my guess i cant be sure.

I've also seen that when two cores are running it doesn't seem to be as efficient as I would expect. CPU time stays about constant but elapsed time jumps massively, as Ian_UK has mentioned. Might be that running on all cores on android is a bad, could background processes keep jumping between cores interrupting Boinc greatly increasing the total time? This in turn greatly reduces the efficiency of running two cores versus one as the elapsed time pre result is equivalent between one and two.
----------------------------------------
[Edit 3 times, last edit by Former Member at Jul 15, 2013 7:36:27 PM]
[Jul 15, 2013 7:31:50 PM]   Link   Report threatening or abusive post: please login first  Go to top 
X1900AIW
Cruncher
Joined: Feb 3, 2008
Post Count: 25
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

Tablet with Android 3.2 (corrected) / DualCore Tegra2 @ 1.0 Ghz joined Beta at 11.07.2013 finished x workunits:
- 34 SN2S
- 9 FAHV

No problems so far ... running nonstop. applause
----------------------------------------
[Edit 1 times, last edit by X1900AIW at Jul 17, 2013 12:36:43 PM]
[Jul 16, 2013 10:33:30 AM]   Link   Report threatening or abusive post: please login first  Go to top 
9maMSSuNWXgttyKdZhMemeXmEx8
Senior Cruncher
Puerto Rico
Joined: Feb 20, 2008
Post Count: 191
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

My tests are done using the NativeBOINC client. I haven't had any issues with it running WCG project.

I can confirm, all my tasks are valid.
----------------------------------------


[Jul 16, 2013 12:23:14 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Beta Testing VINA on Android Devices - July 9, 2013 - Issues Thread

The freedom of choice, but don't expect any support running this client... it's the Native developers to keep up with the Berkeley ones to maintain compatibility. That said, the client is not doing the processing, it's the science app, so most of the times it does not matter which agent version you run.
[Jul 16, 2013 12:53:24 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 89   Pages: 9   [ Previous Page | 1 2 3 4 5 6 7 8 9 | Next Page ]
[ Jump to Last Post ]
Post new Thread