| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 30
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Had one too with signal 11, one beta, nauseatingly, again during a battery charge / discharge cycling because the usb could not keep up with the power demand.
749 9/11/2014 11:34:01 AM Resuming computation 750 World Community Grid 9/11/2014 11:46:31 AM Computation for task BETA_FAHV_x2BBB-AS_0879646_0163_1 finished 751 World Community Grid 9/11/2014 11:46:31 AM Output file BETA_FAHV_x2BBB-AS_0879646_0163_1_0 for task BETA_FAHV_x2BBB-AS_0879646_0163_1 absent 752 World Community Grid 9/11/2014 11:46:31 AM Resuming task BETA_FAHV_x2BBB-AS_0879646_0087_1 using beta18 version 732 in slot 0 753 World Community Grid 9/11/2014 11:48:07 AM Sending scheduler request: To report completed tasks. 754 World Community Grid 9/11/2014 11:48:07 AM Reporting 1 completed tasks The count for signal 11 now stands at 16 of 166 going out with a bang for version 7.16 and this beta combined. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The all distributed was maybe extended, because just now netted a _1 copy
Project Name: Beta - FightAIDS@Home - Vina Created: 09/10/2014 15:17:50 Name: BETA_FAHV_x2BBB-AS_0879646_0380 Minimum Quorum: 2 Replication: 2 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time / Elapsed Time (hours) Claimed/ Granted BOINC Credit BETA_ FAHV_ x2BBB-AS_ 0879646_ 0380_ 1-- - In Progress 9/11/14 10:54:29 9/15/14 10:54:29 0.00 0.0 / 0.0 BETA_ FAHV_ x2BBB-AS_ 0879646_ 0380_ 0-- - In Progress 9/11/14 08:30:09 9/15/14 08:30:09 0.00 0.0 / 0.0 Maybe it could not find a device home till now, certainly if there's 2:24 hours inbetween _0 and _1 to go out, does not suggest there's a big population to participate, and help test if they can be broken. The breaking part is already answered afaiac, they do, just no 195's yet being reported. Hope the technicians do look at the beta testing devices what their specific 195 / 193 history was compared to this test to discern improvement. |
||
|
|
Yarensc
Advanced Cruncher USA Joined: Sep 24, 2011 Post Count: 136 Status: Offline Project Badges:
|
I had one exit in the middle of the night with code 2. The phone was plugged in and should have been at 100% charge, so the WU shouldn't have been starting and stopping at that point. The only thing I can think of on my end that could have caused it is the most recent Android update enabled 'deep sleep' or 'super eco mode' or something like that for, I presume, larger power savings over night.
BOINC 7.4.14; HTC One; KitKat; 3/4 cores running WU's |
||
|
|
Labinopper
Advanced Cruncher Joined: Sep 5, 2013 Post Count: 74 Status: Offline Project Badges:
|
I'm running a HTC One too, 4 cores, but only 3 active (as 4 tends to drain the battery faster than my charger) picked up 6 BETA units
----------------------------------------3 in progress 10:50:39 @ 38% 10:33:28 @ 31% 02:08:27 @ 05% 3 have Errored out @ 08:40:45 Computation error (139,) (according to BoincTasks 1.63) 00:41:42 Computation error (139,) (according to BoincTasks 1.63) 04:41:53 Computation error (124,) (according to BoincTasks 1.63) This is the end of the Status for the longer running WU (NOTE: Wingman has completed this one successfully) [13:05:56] Finished task #56 [13:05:56] Starting task 57 [13:05:56] ./ZINC40477800.pdbqt size = 27 7 ../../projects/www.worldcommunitygrid.org/beta18.x2BBB-AS.pdbqt size = 1849 0 VINA Launched...Initializing...Running...SIGSEGV: segmentation violation #00 pc bce63340 <unknown> (???) [0x] #01 pc 00102688 /data/data/sk.boinc.nativeboinc/files/boinc/projects/www.worldcommunitygrid.org/wcgrid_b (_ZL21worker_signal_handleri+0x14) [0xebfbff91] </stderr_txt> ]]> Also run a Kindle Fire HD which stays plugged in, which has more or less a 100% return rate based on previous experience (unlike my HTC One which runs at around 33% return rate) which has picked up 2 BETA units, currently both at approx 23:30:00 one is at 96% the other at 77% Also as a sidenote, if all 5 units return at 25:00:00 on average, that'll get me my Bronze Badge ;) heres hoping for no errors!! If any further info is needed just ask, hope it helps =) ![]() [Edit 1 times, last edit by Labinopper at Sep 11, 2014 10:52:39 PM] |
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges:
|
So far I got 8 BETA wu on 3 devices. 7 are still in progress and 1 is pv.
----------------------------------------Edit: Beta wu are flowing . In total I have/had 12 on 3 devices. 3 are now in pending validation. I stopped boinc once a while on these devices and also tested reboots and cutting power off.![]() [Edit 1 times, last edit by Eric_Kaiser at Sep 12, 2014 1:36:45 PM] |
||
|
|
Psalm103
Cruncher Joined: Jan 6, 2007 Post Count: 25 Status: Offline Project Badges:
|
Got 1 WU and it ran successfully. I had my phone running hot (both cores crunching), so there were lots of pauses for battery cooling. It took 21 cpu hours to complete, but it's a slow device, so that's typical for a full production WU.
|
||
|
|
KWSN - A Shrubbery
Master Cruncher Joined: Jan 8, 2006 Post Count: 1585 Status: Offline |
Getting valid results. Typically this project returned a lot of invalid which is why I stopped running them on the phone.
----------------------------------------Looking good. ![]() Distributed computing volunteer since September 27, 2000 |
||
|
|
Dark Angel
Veteran Cruncher Australia Joined: Nov 11, 2005 Post Count: 728 Status: Offline Project Badges:
|
Managed to snag a couple of these.
----------------------------------------One is pending, the other in error. Nexus 5, not rooted, default BOINC settings, all OS updates installed Unit log seems ok up to: [22:00:19] Starting task 80 [22:00:19] ./ZINC16002273.pdbqt size = 31 6 ../../projects/www.worldcommunitygrid.org/beta18.x2BBB-AS.pdbqt size = 1849 0 VINA Launched...Initializing...Running...SIGSEGV: segmentation violation #00 pc 0001f20c <unknown> (???) [0x40083257] #01 pc 00102688 /data/data/edu.berkeley.boinc/client/projects/www.worldcommunitygrid.org/wcgrid_beta18_v (_ZL21worker_signal_handleri+0x14) [0xebfbff91] </stderr_txt> ![]() Currently being moderated under false pretences |
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges:
|
As of now I received ~25 Beta wu on 5 different android devices. They run 4 different android os versions up to the latest kitkat. No errors so far. Some of the Beta wu are resends and so far I have seen the errors on other participants were all signal 11 (didn't check all).
----------------------------------------8 wu are still in progress. 6 valid and the rest is pending validation. ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The signal 11 are mine probably,
---------------------------------------- . Three of 15 so far went out with this, though the cpu load pause was set down to 10 percent. One went with code 26, of which my device seems to be the only one ever to incur these, the 3rd time now including production.Overall, the number of copies distributed is way down from my 6.6 to this beta at 2.3. They run long, seen now one with 21 hours, so those are nail-biters, as in 'do the make it to term before a signal 11 condition develops?'. Stats so far, most stuck in pending. Efficiency still better than the version 7.16, this 7.32 a seeming huge step, indicating there's been many alpha tests in between before considered good enough to try a beta again: ![]() Trusting the pending will turn valid, in runtime hours version 7.32 would hit 89 percent ok. This compares to 84% for the first 100 that were detail logged for version 7.16. Starting to see repairs now, so think the originals are slowly running out. They're rush processing with just over 1 day deadline. 2 of 4 now in high priority. Obviously maintaining the 'good' level for devices that were doing fairly well is not the main mission though, it's the devices that had persistent fails with the 195 and 193. Here these are as frequent as blue moons. If though 89 percent good versus 84 percent is an indicator, we might finally be looking at a 'stable' app for many more. The hateful 'output file absent' maybe remaining as issue to address. Fear if it is, it won't be easy 567 World Community Grid 9/13/2014 8:28:07 PM Computation for task BETA_FAHV_x2BBB-AS_0879646_0287_1 finished 568 World Community Grid 9/13/2014 8:28:07 PM Output file BETA_FAHV_x2BBB-AS_0879646_0287_1_0 for task BETA_FAHV_x2BBB-AS_0879646_0287_1 absent 569 World Community Grid 9/13/2014 8:28:07 PM Resuming task FAHV_x2AVV-A-AS_0879341_0197_0 using fahv version 716 in slot 1 570 World Community Grid 9/13/2014 8:29:49 PM Sending scheduler request: To report completed tasks. 571 World Community Grid 9/13/2014 8:29:49 PM Reporting 1 completed tasks Here's hoping. [Edit 1 times, last edit by Former Member at Sep 14, 2014 8:56:38 AM] |
||
|
|
|