Test run frequency on TestToolShed

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Test run frequency on TestToolShed

Peter Cock
Hi all,

Are the main and test tool-sheds currently meant to
be running the tool functional tests every 48 hours?

I created and updated these repositories last week,
but they have yet to be tested:

https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_composition
https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh

Thanks,

Peter

P.S. it would be nice to be able to sort the "Repositories I
own" lists etc by date (particularly for my typical workflow
of posting an update to the TestToolShed, waiting for a
green light from the tests, and then pushing this to the
main ToolShed).
___________________________________________________________
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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Test run frequency on TestToolShed

Peter Cock
On Mon, Aug 18, 2014 at 11:16 AM, Peter Cock <[hidden email]> wrote:

> Hi all,
>
> Are the main and test tool-sheds currently meant to
> be running the tool functional tests every 48 hours?
>
> I created and updated these repositories last week,
> but they have yet to be tested:
>
> https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_composition
> https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh
>
> Thanks,
>
> Peter
>
> P.S. it would be nice to be able to sort the "Repositories I
> own" lists etc by date (particularly for my typical workflow
> of posting an update to the TestToolShed, waiting for a
> green light from the tests, and then pushing this to the
> main ToolShed).

Perhaps something deeper here, older untested examples:

Revised 2014-07-30 ,
https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_filter_by_id
https://testtoolshed.g2.bx.psu.edu/view/peterjc/blastxml_to_top_descr

Revised 2014-07-31,
https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast2go

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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Test run frequency on TestToolShed

Dave Bouvier
Peter,

The tests are configured to run once every 48 hours, on even-numbered days of the month. I'll be looking into the three you mentioned in your second email to determine why they are not being tested, or why the test results are not being updated.

--Dave B.
On 08/18/2014 07:28 AM, Peter Cock wrote:

> On Mon, Aug 18, 2014 at 11:16 AM, Peter Cock <[hidden email]> wrote:
> > Hi all,
> >
> > Are the main and test tool-sheds currently meant to
> > be running the tool functional tests every 48 hours?
> >
> > I created and updated these repositories last week,
> > but they have yet to be tested:
> >
> > https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_composition
> > https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh
> >
> > Thanks,
> >
> > Peter
> >
> > P.S. it would be nice to be able to sort the "Repositories I
> > own" lists etc by date (particularly for my typical workflow
> > of posting an update to the TestToolShed, waiting for a
> > green light from the tests, and then pushing this to the
> > main ToolShed).
>
> Perhaps something deeper here, older untested examples:
>
> Revised 2014-07-30 ,
> https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_filter_by_id
> https://testtoolshed.g2.bx.psu.edu/view/peterjc/blastxml_to_top_descr
>
> Revised 2014-07-31,
> https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast2go
>
> 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:
>    http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>    http://galaxyproject.org/search/mailinglists/
>

___________________________________________________________
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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/
Reply | Threaded
Open this post in threaded view
|

Re: Test run frequency on TestToolShed

saketkc
Dave,

I have similar issues with my repositories:
https://testtoolshed.g2.bx.psu.edu/view/saketkc/pycurl_test

This was uploaded on 14th August.

https://testtoolshed.g2.bx.psu.edu/view/saketkc/package_pycurl_7_19_3_1

shows no test results for the month of August. The last test was run on
2014-07-28

Saket

On 18 August 2014 06:33, Dave Bouvier <[hidden email]> wrote:

> Peter,
>
> The tests are configured to run once every 48 hours, on even-numbered days
> of the month. I'll be looking into the three you mentioned in your second
> email to determine why they are not being tested, or why the test results
> are not being updated.
>
> --Dave B.
>
> On 08/18/2014 07:28 AM, Peter Cock wrote:
>>
>> On Mon, Aug 18, 2014 at 11:16 AM, Peter Cock <[hidden email]>
>> wrote:
>> > Hi all,
>> >
>> > Are the main and test tool-sheds currently meant to
>> > be running the tool functional tests every 48 hours?
>> >
>> > I created and updated these repositories last week,
>> > but they have yet to be tested:
>> >
>> > https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_composition
>> > https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast_rbh
>> >
>> > Thanks,
>> >
>> > Peter
>> >
>> > P.S. it would be nice to be able to sort the "Repositories I
>> > own" lists etc by date (particularly for my typical workflow
>> > of posting an update to the TestToolShed, waiting for a
>> > green light from the tests, and then pushing this to the
>> > main ToolShed).
>>
>> Perhaps something deeper here, older untested examples:
>>
>> Revised 2014-07-30 ,
>> https://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_filter_by_id
>> https://testtoolshed.g2.bx.psu.edu/view/peterjc/blastxml_to_top_descr
>>
>> Revised 2014-07-31,
>> https://testtoolshed.g2.bx.psu.edu/view/peterjc/blast2go
>>
>> 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:
>>    http://lists.bx.psu.edu/
>>
>> To search Galaxy mailing lists use the unified search at:
>>    http://galaxyproject.org/search/mailinglists/
>>
>
> ___________________________________________________________
> 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:
>  http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>  http://galaxyproject.org/search/mailinglists/
___________________________________________________________
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:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/