After fixing a number of issues, it appears that the tests are now
running as they should. I'll keep an eye on the test framework in case
any new errors crop up.
On 12/10/2014 09:19 AM, Peter Cock wrote:
On Wed, Dec 10, 2014 at 2:03 PM, John Chilton
> On Wed, Dec 10, 2014 at 5:46 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
>> Hi guys,
>> The good news is my list of failing tools has shrunk to the following,
>> none of which seem to have been tested yet in December, stuck
>> with "Exception: Job in error state.":
>> Meanwhile, on the main tool, "Exception: Job in error state."
>> and not yet tested in December:
>> It would be nice to have a more informative error here...
> Ugh - yes it clearly would - very sorry about that.
>> Have these tools been automatically earmarked not to be retested?
>> Note that some tools have been tested earlier this month:
>> I also have a legitimate failure for missing tests, run 2014-12-09,
> Interesting... some tests did run though? Does the framework not
> report passing tests - seems like it would be hard to know if it
> working in that case.
The "Latest revision: all tool tests pass" search returns lots of
repositories, but I must examine each one-by-one to see when
the tests were last run. The sample I just checked on the main
Tool Shed were all lasted tested 2014-11-23,
However at least some tests have been run in December, e.g.
Things seem similar on the Test Tool Shed. Presumably you
can sort the test results over the entire Tool Shed via a
database search? That might help explain any pattern here.