Peter, 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,
http://testtoolshed.g2.bx.psu.edu/view/peterjc/blast2go/f3a61c2cf309 - can see test failure, good.
http://testtoolshed.g2.bx.psu.edu/view/peterjc/effectivet3/392279f2e120 - shows one passing test (which is odd, where is the failure?)
http://testtoolshed.g2.bx.psu.edu/view/peterjc/get_orfs_or_cdss/26ce6e046040 - no test results visible
http://testtoolshed.g2.bx.psu.edu/view/peterjc/mira_assembler/da604cc07658 - can see test failure, good.
http://testtoolshed.g2.bx.psu.edu/view/peterjc/nlstradamus/2be36fa7565e - some test results visible, but no failures
http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_rename/44b2e489e26f - no test results visible
http://testtoolshed.g2.bx.psu.edu/view/peterjc/tmhmm_and_signalp/4cd848c5590... - no test results visible (strange, should be skipping the tests, so why is this listed as failing?)
http://testtoolshed.g2.bx.psu.edu/view/peterjc/venn_list/51fe47a5a803 - 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?
Regards,
Peter