Hi Dave, Can you check for stalls on the following repositories please? They've not been tested for nearly two months: https://toolshed.g2.bx.psu.edu/view/peterjc/clinod Last tested 2015-01-29, Exception: Job in error state. https://toolshed.g2.bx.psu.edu/view/peterjc/blast2go Last tested 2015-01-29, Exception: Job in error state. https://toolshed.g2.bx.psu.edu/view/peterjc/effectivet3 Last tested 2015-01-29, Exception: Job in error state. https://toolshed.g2.bx.psu.edu/view/peterjc/samtools_depad Last tested 2015-01-29, Converting local (test-data) bam to sam failed The cause of the last failure is different (and is also failing on the Test Tool Shed), raised separately here: https://lists.galaxyproject.org/pipermail/galaxy-dev/2015-March/021650.html http://dev.list.galaxyproject.org/test-base-twilltestcase-py-Converting-loca... -- Could you tweak the "Latest revision: failing tool tests" output to include the date last tested in the table of results? Over on the test tool shed there are plenty of recent failures which I will email about separately - I'll report back here if I spot any more stall entries where there tests look backlogged. Thanks, Peter On Wed, Mar 18, 2015 at 1:46 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Gentlemen,
The issue with the nightly testing was due to a stalled test run blocking subsequent tests. I've cleared out that blockage and a manual test run appears to have completed successfully, as should future automated test runs. As always, feel free to let us know if you encounter any additional inexplicable behavior.
--Dave B.