Hello all,

I am currently hoping to review the automated test results for
some repositories which I have recently updated, in one case
for dependency handling, the other functional changes:

https://testtoolshed.g2.bx.psu.edu/view/peterjc/mummer
https://testtoolshed.g2.bx.psu.edu/view/peterjc/ncbi_blast_plus

These have not yet been tested. On further investigation
of a sample of my other tools, it appears none of them have
been tested on the Test Tool Shed since 2014-09-15, e.g.

https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_rename
https://testtoolshed.g2.bx.psu.edu/view/peterjc/sample_seqs
https://testtoolshed.g2.bx.psu.edu/view/peterjc/samtools_idxstats
https://testtoolshed.g2.bx.psu.edu/view/peterjc/effectivet3
https://testtoolshed.g2.bx.psu.edu/view/peterjc/clinod

Similarly, some of my tools on the Main Tool Shed appear
not to have been tested since 2014-09-21, e.g.

https://toolshed.g2.bx.psu.edu/view/peterjc/seq_rename
https://toolshed.g2.bx.psu.edu/view/peterjc/effectivet3
https://toolshed.g2.bx.psu.edu/view/peterjc/clinod

or 2014-10-27,

https://toolshed.g2.bx.psu.edu/view/peterjc/sample_seqs
https://toolshed.g2.bx.psu.edu/view/peterjc/samtools_idxstats

Is there a known problem with the automated tool testing
(previously every second night) on the Tool Sheds?
Or have you had to further reduce the testing cycle?

Testing less frequently seems fine, say fortnightly, if this can
be supplemented by testing updated tools everynight. That
would give Tool Authors prompt feedback on their updates,
but also catch regressions where changes in Galaxy break
a previously working tool.

Regards,

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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/

Reply via email to