On Wed, Aug 21, 2013 at 10:54 AM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
On Tue, Aug 20, 2013 at 9:15 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Peter,
I believe this was again due to the installation of an earlier repository hanging until the testing framework canceled the build. I've added the repository in question to the exclude list, and hopefully your blast repositories will be properly tested within the next few hours.
--Dave B.
Thanks Dave,
Re: http://testtoolshed.g2.bx.psu.edu/view/peterjc/ncbi_blast_plus/946749c8605f
The output has changed, but we're back to missing any test results at all now, all I get is:
... Automated tool test results
Tool test results Automated test environment Time tested: ~ 10 hours ago System: Linux 3.8.0-25-generic Architecture: x86_64 Python version: 2.7.4 Galaxy revision: 10419:4f4e01316260 Galaxy database version: 115 Tool shed revision: 10413:6e148e87d819 Tool shed database version: 21 Tool shed mercurial version: 2.2.3
Automated tool tests ...
Test results now visible now (odd?), back to the install problem: Fatal error: Exit code 127 () /bin/sh: 1: blastn: not found /bin/sh: 1: blastn: not found Any clues from the Test Tool Shed log file would be helpful, Thanks, Peter