It turns out that the automated functional testing framework was not actually running. I suggest having a look in the morning, and if there are still any missing test results, I'll get them resolved then.

   --Dave B.

On 6/25/13 02:10:10.000, Peter Cock wrote:
Hi again Dave,

Have you worked out any possible causes for missing test results?
I do suspect some sort of caching issue is to blame...

Here is the current list of my failing repositories from the Test
Tool Shed,
- can see test failure, good.
- shows one passing test (which is odd, where is the failure?)
- no test results visible
- can see test failure, good.
- some test results visible, but no failures
- no test results visible
- no test results visible (strange, should be skipping the tests, so
    why is this listed as failing?)
- can see test failure, good.

Note that for get_orfs_or_cdss and seq_rename, I am trying to
use an automatically installed dependency on Biopython - so
perhaps there is a silent dependency failure which means the
tests are not being run?



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