| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: OpenPandemics - COVID 19 Beta Test April 20, 2020 [ Issues Thread ] |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 303
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For uplinger: Just received 3 Beta _2 and _3 issues with app build 7.15 on Android. Since the latest iteration is 7.17, is there any point in putting 30-32 hours into each of these when we know the 7.15 code is not picture perfect? If not, I'd rather abort them and let someone else acquire the hours. Edit: Each of these already have a Pending Validation copy and a No Reply + Error wingman. Lavaflow, If you abort them, then it'll add towards the count of total results allowed per work unit. Which may cause the entire work unit to stop. It is fine to let 7.15 to run as we are still looking at the error/invalid rates to make sure they are within range for other applications. The changes between 7.15 and 7.17 for Android is nothing major. The changes were primarily around increasing precision and graphics for linux 64 bit. Thanks, -Uplinger OK, they're really really slowly progressing, 31.5% after 21 hours. The deadline is May 13 04:58, which may explain all 3 suffered a No Reply and got me the extra copy. All 3 No Reply meantime did a User Abort probably concluding too they were not going to make the deadline. I'll let them plot on as they no doubt will get there before the final _4 copy get completed and becomes redundant. On the graphics, only peaked, not a watcher, noticed that when hitting 'show graphics', the window that opens is too small to fit the complete graphics but then HSTb does neither, nor ARP1. Resizing the graphics frame and reopening shows it's not remembering the size of the graphics window i.e. back to too small. Client 7.14.2, Windows 10 64 2005. Something to fix for the candy lovers. |
||
|
|
Aurum
Master Cruncher The Great Basin Joined: Dec 24, 2017 Post Count: 2384 Status: Offline Project Badges: 
|
Be nice to purge all older betas that are still Pending before starting a new run. I still have many 334-337 Pending Validation. For the 34s I haven't gotten any Invalids yet but the first to be Valid has a wingman that Errored out using a BOINC version I don't recognize:
----------------------------------------Result Name: BETA_ OPN1_ 0000034_ 08846_ 1-- <core_client_version>7.6.31</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> INFO:[08:36:15] Start AutoGrid... autogrid4: Successful Completion. INFO:[08:36:51] End AutoGrid... INFO:[08:36:51] Start AutoDock for ZINC001188705448-ACR3.45_RX1--4mm3_001_tyr264-HO--CYS112_wcgsplit3.dpf(Job #0)... INFO: In AutoDock main_autodock() Beginning AutoDock... SIGBUS: bus error Stack trace (9 frames): [0x4729b2] [0x52b1b0] [0x44be4c] [0x425042] [0x459a4c] [0x4034b7] [0x52c844] [0x52cac1] [0x404066] Exiting... </stderr_txt> ]]>   ...KRI please cancel all shadow-banning[Edit 2 times, last edit by Aurum420 at May 12, 2020 11:29:08 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
SIGSEGV and SIGBUS are captured by BOINC under the same 193 error it shows, the difference explained, respective Linux signal errors 11 and 10.
----------------------------------------https://www.geeksforgeeks.org/segmentation-fault-sigsegv-vs-bus-error-sigbus/ The main difference between Segmentation Fault and Bus Error is that Segmentation Fault indicates an invalid access to a valid memory, while Bus Error indicates an access to an invalid address. [Edit 1 times, last edit by Former Member at May 12, 2020 11:42:53 AM] |
||
|
|
Aurum
Master Cruncher The Great Basin Joined: Dec 24, 2017 Post Count: 2384 Status: Offline Project Badges:
|
My second Valid has the same Error from two wingmen as the first. I sure hope we're not holding up this project for a small Android cohort.
----------------------------------------Result Name: BETA_ OPN1_ 0000034_ 05422_ 0-- <core_client_version>7.4.53</core_client_version> <![CDATA[ <message> process exited with code 255 (0xff, -1) </message> <stderr_txt> reloc_library[1322]: 8171 cannot locate 'statvfs'... CANNOT LINK EXECUTABLE </stderr_txt> ]]> ...KRI please cancel all shadow-banning |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Uplinger has already stated that any issues with Android would not hold up the launch of the project.
|
||
|
|
Aurum
Master Cruncher The Great Basin Joined: Dec 24, 2017 Post Count: 2384 Status: Offline Project Badges:
|
Uplinger has already stated that any issues with Android would not hold up the launch of the project. Excellent. Sorry I overlooked his comment. Then launch may be imminent :-)...KRI please cancel all shadow-banning |
||
|
|
Pete Broad
Senior Cruncher Wales Joined: Jan 3, 2007 Post Count: 167 Status: Offline Project Badges: 
|
I've had approx 150 Android units. Except for 6 in progress all have been validated successfully.
----------------------------------------Pete  |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges:
|
Not really important to the project, but ...
I happened to observe one of the betas (Windows or Intel Linux) as it approached completion. It would get to within 30 sec of estimated finish time / 99-point-something complete, then suddenly drop back to about 2 min from EFT / 98-point-something complete, and repeat. I saw it do this about 5 times before it got to the 100% line. I don't recall FAAH-AutoDock doing that. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7545 Status: Offline Project Badges:
|
All these had the same error on a Linux machine running a live copy on a USB drive. I think what happened was they ran out of storage space on the drive due to a coupe of ARP units. All of the Beta's had run fine when I was only running SCC units exclusively, but evidently the ARP units use a lot more storage space. This probably won't affect anybody else unless they are really tight on available storage.
----------------------------------------BETA_ OPN1_ 0000034_ 04895_ 1-- mint Error 5/12/20 03:09:11 5/12/20 07:05:47 0.01 / 0.01 0.2 / 0.0 BETA_ OPN1_ 0000034_ 02051_ 0-- mint Error 5/12/20 03:07:07 5/12/20 07:05:47 0.01 / 0.01 0.2 / 0.0 BETA_ OPN1_ 0000034_ 09146_ 0-- mint Error 5/12/20 03:05:04 5/12/20 07:05:47 0.01 / 0.01 0.2 / 0.0 BETA_ OPN1_ 0000034_ 11441_ 1-- mint Error 5/12/20 03:00:52 5/12/20 07:05:47 0.01 / 0.01 0.3 / 0.0 BETA_ OPN1_ 0000034_ 11062_ 0-- mint Error 5/12/20 02:58:49 5/12/20 07:05:47 0.01 / 0.01 0.3 / 0.0 BETA_ OPN1_ 0000034_ 10759_ 1-- mint Error 5/12/20 02:55:53 5/12/20 12:26:32 0.01 / 0.03 0.6 / 0.0 BETA_ OPN1_ 0000034_ 08846_ 1-- mint Error 5/12/20 02:52:02 5/12/20 08:45:16 0.01 / 0.01 0.3 / 0.0 BETA_ OPN1_ 0000034_ 05803_ 0-- mint Error 5/12/20 02:52:02 5/12/20 08:45:16 0.01 / 0.01 0.3 / 0.0 BETA_ OPN1_ 0000034_ 14297_ 0-- mint Error 5/12/20 02:51:41 5/12/20 12:26:32 0.01 / 0.03 0.6 / 0.0 BETA_ OPN1_ 0000034_ 05422_ 2-- mint Error 5/12/20 02:49:54 5/12/20 08:45:16 0.01 / 0.01 0.3 / 0.0 BETA_ OPN1_ 0000034_ 01424_ 0-- mint Error 5/12/20 02:49:38 5/12/20 12:26:32 0.23 / 0.24 4.7 / 0.0 BETA_ OPN1_ 0000034_ 03578_ 1-- mint Error 5/12/20 02:47:34 5/12/20 12:26:32 0.32 / 0.32 6.3 / 0.0 BETA_ OPN1_ 0000034_ 00626_ 1-- mint Error 5/12/20 02:45:31 5/12/20 12:26:32 0.65 / 0.65 12.8 / 0.0 BETA_ OPN1_ 0000034_ 15755_ 0-- mint Error 5/12/20 02:43:28 5/12/20 12:26:32 0.65 / 0.65 12.8 / 0.0 BETA_ OPN1_ 0000034_ 15237_ 1-- mint Error 5/12/20 02:41:24 5/12/20 12:26:32 0.80 / 0.80 15.7 / 0.0 BETA_ OPN1_ 0000034_ 01664_ 1-- mint Error 5/12/20 02:39:21 5/12/20 12:26:32 0.89 / 0.89 17.4 / 0.0 BETA_ OPN1_ 0000034_ 01398_ 1-- mint Error 5/12/20 02:37:17 5/12/20 12:26:32 1.14 / 1.14 22.4 / 0.0 BETA_ OPN1_ 0000034_ 05704_ 1-- mint Error 5/12/20 02:35:14 5/12/20 12:26:32 1.36 / 1.36 26.7 / 0.0 BETA_ OPN1_ 0000034_ 06793_ 1-- mint Error 5/12/20 02:33:10 5/12/20 12:26:32 1.52 / 1.52 29.8 / 0.0 BETA_ OPN1_ 0000034_ 03243_ 1-- mint Error 5/12/20 02:31:06 5/12/20 12:26:32 1.61 / 1.61 31.6 / 0.0 Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
All these had the same error on a Linux machine running a live copy on a USB drive. I think what happened was they ran out of storage space on the drive due to a coupe of ARP units. All of the Beta's had run fine when I was only running SCC units exclusively, but evidently the ARP units use a lot more storage space. This probably won't affect anybody else unless they are really tight on available storage. It caught me a little while back after converting to CentOS. CentOS installer had allocated minimal storage to /root and most of the rest to /home. Since /var is in the /root filesystem, it filled up. Had to reconfigure my filesystems. Luckily, the installer used LVM so the reconfigure was easy. ARP and Rosetta filled it up fast. |
||
|
|
|