On Wed, Dec 10, 2014 at 5:46 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
On Thu, Nov 27, 2014 at 1:58 PM, Peter Cock
> Hi Guys,
> I retitled this since the TestToolShed does seem to be running tests
> regularly again. However, I still have a fair number failing with the
> cryptic status "Exception: History in error state."
> I guess the logging changes John tried are not propagated to the
> user-facing output on the ToolShed, but might still offer you some
> It appears from the stack trace to be something with uploading
> the test input files into the new history?
> My current list of tools with failing tests is:
> I have updated some of the tools I listed below (in the older email),
> so their latest revision has not yet been tested.
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.
And again, a legitimate failure for some missing tests on the
main Tool Shed, also run on 2014-12-09,