Hi Dave,

Progress: I can now see the test failures which suggest that the
underlying binaries did not get installed properly. I guess this
either means:

(a) the dependency install failed but the Tool Shed doesn't say
this (my hunch as recently the NCBI BLAST+ tools had stopped
compiling on the Test Tool Shed due to a BOOST system library


(b) the dependency installed didn't raise any errors but failed
in some way such as not setting the path (unlikely as the
tool_dependencies.xml content has not changed - it has
just been moved to a dependency package repository)


(c) there is something amiss with the dependency chain meaning
that the BLAST dependencies are not being added to the PATH.
This looks OK but it is the only thing I have changed recently.

Or some other mode of failure I'm not guessed at yet?

Is this something you can diagnose, or do I need to press
ahead with a local Tool Shed to help me work out what is



On Fri, Aug 9, 2013 at 1:58 PM, Dave Bouvier <d...@bx.psu.edu> wrote:
> Peter,
> The automated build prior to this email was executed incorrectly. I've
> resolved that status, and the current test results look correct.
>    --Dave B.
> On 8/8/13 10:30:37.000, Peter Cock wrote:
>> I've been updating the BLAST+ repository - currently it does
>> show some failures due to missing test, but there seems to be
>> test information missing here - and also I'm expecting the
>> installation to fail with BOOST issues:
>> http://testtoolshed.g2.bx.psu.edu/view/peterjc/ncbi_blast_plus/5693417851ec
>> (The other problems from 1 August look OK now)
>> Thanks,
>> Peter
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to