The good news is yes, the tests are running again on the
Test Tool Shed (although not the main Tool Shed yet), and
many of my tools now have successful test results from
e.g. My new basic mummer tool which now has a full set
of dependency packages thanks to Bjoern:
The bad news is there are many unexpected failures with:
"Exception: History in error state."
I'm sure you'll learn more once you look over the logs,
On Wed, Nov 5, 2014 at 6:21 PM, Dave Bouvier <dave(a)bx.psu.edu> wrote:
This was due to a number of issues with the testing framework, the last of
which appears to have been resolved, and I see tools being tested in the
framework log. I'll check again in the morning to see if any of the tools
you listed below were still not tested.
On 11/03/2014 05:51 AM, Peter Cock wrote:
> 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:
> 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.
> Similarly, some of my tools on the Main Tool Shed appear
> not to have been tested since 2014-09-21, e.g.
> or 2014-10-27,
> 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.
> 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: