Hello Peter,

I've done a significant amount of re-engineering of the Tool Shed's install and 
test framework over the past 2 weeks, so the results you are seeing are 
probably a reflection of some broken peices during the time frame in which I 
was making changes.  I believe I have most of the things ironed out in 
11545:32205f911e74 which is now running on the test tool shed.  

We will be performing some test runs of thie new framework over the long 
weekend, so more correct test results should hopefully be showing up for yours 
and other repositories.  

I've also enhanced the "Tool test results" components to store a configurable 
number of test runs instead of just 1.  The test tool shed is configured to 
store 5 test runs.  So from here on you'll begin to see multiple containers in 
the Tool test results container - something like this:

Automated tool test results

2013-11-27 15:49:51                                              
Automated test environment                                              
Tests that passed successfully                                              
2013-11-27 15:17:57                                              
Automated test environment                                              
Tests that passed successfully                                              
2013-11-27 14:53:46                                              
Automated test environment                                              
Tests that passed successfully                                              
2013-11-27 14:50:30                                              
Automated test environment                                              
Tests that passed successfully                                              

We'll keep on top of things that need fixing as we proceed with this new 


Greg Von Kuster

On Nov 27, 2013, at 5:44 AM, Peter Cock <p.j.a.c...@googlemail.com> wrote:

> On Thu, Nov 21, 2013 at 2:47 PM, Peter Cock <p.j.a.c...@googlemail.com> wrote:
>> On Thu, Nov 21, 2013 at 2:38 PM, Dave Bouvier <d...@bx.psu.edu> wrote:
>>> Peter,
>>> About three weeks ago, we began to focus a higher priority on fixing the
>>> nightly functional test runs.
>> And we're starting to see the dividends of this time investment now :)
> Hi Dave,
> For a while almost all my tools were showing as passing their tests,
> but sadly something seems to have broken - has the Test Tool Shed
> really not run any tests for the last three days? Even if so, the display
> is still missing the last test results.
> Test Tool Shed, "Latest revision: installation errors", no individual test
> results, but says the tests were run ~4 days ago:
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/blast2go/8c462f7b2c8d
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/effectivet3/1e681e19e35c
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/fastq_paired_unpaired/63eb4456bf71
> Test Tool Shed, "Latest revision: installation errors", but no test results
> section at all:
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/get_orfs_or_cdss/09b5b1af9b8f
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/ncbi_blast_plus/b2795652d2b4
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_primer_clip/42bca649ec44
> Actual test failure shown, again time tested listed as 4 days ago, but
> apparently a framework issue:
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/nlstradamus/81cac85fc286
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_filter_by_id/324893f5751e
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_rename/61cec46f6be5
> http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_select_by_id/bedfe8f3d3fb
> (BrowserStateError: cannot go to 'http://None:29009')
> Regards,
> Peter

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