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.
On Wed, Nov 19, 2014 at 5:57 PM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
Fingers crossed we'll get some more detailed logs in a day or two :)
On Wed, Nov 19, 2014 at 5:48 PM, John Chilton <jmchilton(a)gmail.com> wrote:
> Hey Peter,
> Dave is out this week - so I have tried to fumble around and see if I
> could make some progress on this. I found some bugs in a recent commit
> and fixed them - that might help
> I also have enabled more verbose logging that might help those
> "History in error state" exceptions
> but I am not sure it will propagate through to the tool shed API - we
> will see I guess.
> If the install and test framework just picks up the latest central -
> these fixes will hopefully be reflected in the next run.
> On Wed, Nov 19, 2014 at 4:48 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote:
>> Hi Dave,
>> Any progress? All the following seem to have been tested
>> in the last few days on the TestToolShed, but failed with
>> "Exception: History in error state."
>> That's about half of my TestToolShed repositories - most
>> of the others report their tests passed :)
>> I am also seeing unexpected problems with packages, e.g.
>> Error getting revision e78bbab7933d of repository
>> package_blast_plus_2_2_29 owned by iuc: An entry for the repository
>> was not found in the database.