Dan, I looked at the testout.Aug21-2013-1438.tgz file. Several of the .txt files start with bash: line 0: cd: /kb/dev_container/modules/clients: No such file or directory This seems to correspond to the "exit code 2" in your testing errors. Is there perhaps a typo? When testing client-only modules, I would have expected to: 1. ssh clients 2. cd /kb/dev_container/modules/<module_name> I believe that kb_seed needs a longer timeout. It has extremely long tests. I'll look into the others. Miriam On 8/24/13 11:23 AM, "Dan Olson" <[email protected]> wrote:

Release team,

I think the automated testing is fairly complete in the attached version of the build script. There is a timeout set, where tests that take more than 1200 seconds to run are killed off (command timeout).

The long output of all the tests are included in the testout tarball attached.

Next step is automating the VM and DMG creation from this.

----- Forwarded Message ----- From: [email protected] To: [email protected] Sent: Saturday, August 24, 2013 9:23:51 AM Subject: KBase Nightly Build from Aug24-2013-0923

***** AUTOMATED TESTING ERRORS***** assembly: ssh exited with exit code 2 communities_api: ssh exited with exit code 2 communities_qc: ssh exited with exit code 2 erdb_service: ssh exited with exit code 2 experiment: ssh exited with exit code 2 file_type_service: command timeout file_type_service: ssh exited with exit code 143 jnomics: ssh exited with exit code 255 kbapi_common: ssh exited with exit code 255 KBaseFBAModeling: ssh exited with exit code 2 kb_model_seed: ssh exited with exit code 255 kb_seed: command timeout kb_seed: ssh exited with exit code 143 matR: ssh exited with exit code 2 microbes_model_builder: ssh exited with exit code 2 probabilistic_annotation: ssh exited with exit code 2 prom_service: command timeout prom_service: ssh exited with exit code 143 search: ssh exited with exit code 255 shock_service: ssh exited with exit code 2