Hi Dave,

Can you check for stalls on the following repositories please?
They've not been tested for nearly two months:

Last tested 2015-01-29, Exception: Job in error state.

Last tested 2015-01-29, Exception: Job in error state.

Last tested 2015-01-29, Exception: Job in error state.

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:



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.



On Wed, Mar 18, 2015 at 1:46 PM, Dave Bouvier <d...@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.
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