![](https://secure.gravatar.com/avatar/d6e08d6cec942c4f1daeb57fb1e80724.jpg?s=120&d=mm&r=g)
Peter, I've created a Trello card for tracking the status of this issue. https://trello.com/c/32l2NZRn/1048-toolshed-investigate-possibility-of-recor... --Dave B. On 8/14/13 09:40:03.000, Peter Cock wrote:
On Wed, Aug 14, 2013 at 2:32 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Peter,
The problem with testing the installation of package tool dependencies, especially but not limited to BLAST+, is that the time it takes to compile them exceeds the timeout for the automated testing framework, and so it terminates that build step. I am currently working on enhancing the actions tag to support a different install process depending on the target architecture, and hope to have that ready early next week.
--Dave B.
That's useful (and probably explains quite a few 'silent failures').
Could you make sure this time out failure and other install failures are visible on the Tool Shed as part of the test results? I think that is more urgent than tweaking the install target architecture.
Thanks,
Peter