Thanks for the information, it uncovered a problem with the testing framework that has been resolved in 10817:6b0c3592dde1. The listed repositories should start showing useful results next time the nightly tests run.

   --Dave B.

On 10/04/2013 06:19 AM, Peter Cock wrote:
On Fri, Oct 4, 2013 at 11:11 AM, Peter Cock <> wrote:
On Thu, Sep 26, 2013 at 3:29 PM, Dave Bouvier <> wrote:
Ross, Peter,

Unfortunately, there are some issues with the automated testing framework
that I am working on resolving. I've created a Trello card to track my

    --Dave B.

Any joy with that "from fabric.api import env" issue?

Meanwhile the set of tools with missing test failures seems to
change from day to day, right now the following are listed under
"Latest revision: failing tool tests" yet have not test results:
(expected to pass)
(expected to pass)
(expected to pass)


There's a similar set on the main Tool Shed, where I should have the
same version of those three tools, which may be interesting for
tracing the problem(s):
(expected to pass)
(expected to pass)
(expected to pass)

Also missing test results:
(this revision is expected to fail if Biopython not present, see other thread
about packaging NumPy and its dependencies)



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