Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-09 Thread Rainer M Krug
Markus Neteler writes: > On Thu, Jun 9, 2016 at 11:14 AM, Rainer M Krug wrote: > ... >> Just realized the on-failure notification=s are still disabled - please >> see my pull request where I enabled them again. >> >>

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-09 Thread Markus Neteler
On Thu, Jun 9, 2016 at 11:14 AM, Rainer M Krug wrote: ... > Just realized the on-failure notification=s are still disabled - please > see my pull request where I enabled them again. > > https://github.com/GRASS-GIS/grass-ci/pull/2 Done in r68656. Markus

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-09 Thread Rainer M Krug
Rainer M Krug writes: > Markus Neteler writes: > >> On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote: >>> Markus Neteler writes: >>> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: >

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-09 Thread Rainer M Krug
Markus Neteler writes: > On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote: >> Markus Neteler writes: >> >>> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: Markus Neteler writes: >>> ...

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-09 Thread Markus Neteler
On Fri, Jun 3, 2016 at 1:43 PM, Rainer M Krug wrote: > Markus Neteler writes: > >> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: >>> Markus Neteler writes: >> ... Anything to be done there? Was it integrated?

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-08 Thread Rainer M Krug
Just to make sure that this doesn't get lost again. Rainer Rainer M Krug writes: > Markus Neteler writes: > >> On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: >>> Markus Neteler writes: >> ... Anything to be

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-03 Thread Rainer M Krug
Markus Neteler writes: > On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: >> Markus Neteler writes: > ... >>> Anything to be done there? Was it integrated? Or stuck at >>> >>> https://trac.osgeo.org/grass/ticket/2733 >> >> I think it

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-02 Thread Markus Neteler
On Thu, Jun 2, 2016 at 7:59 PM, Rainer M Krug wrote: > Markus Neteler writes: ... >> Anything to be done there? Was it integrated? Or stuck at >> >> https://trac.osgeo.org/grass/ticket/2733 > > I think it was stuck - but I haven't looked at it since and I have

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-02 Thread Rainer M Krug
Markus Neteler writes: > Hi, > > back to this topic: > > On Thu, Sep 3, 2015 at 5:24 PM, Rainer M Krug wrote: >> Hi >> >> is anything happening in regards to the travis-ci integration? I did not >> get any feedback or how I can submit it to the svn. >> >> In

Re: [GRASS-dev] Travis-ci and tests of grass 7

2016-06-02 Thread Markus Neteler
Hi, back to this topic: On Thu, Sep 3, 2015 at 5:24 PM, Rainer M Krug wrote: > Hi > > is anything happening in regards to the travis-ci integration? I did not > get any feedback or how I can submit it to the svn. > > In regards to testing: I know about the python gunit tests

Re: [GRASS-dev] Travis-ci and tests of grass 7

2015-09-07 Thread Rainer M Krug
Vaclav Petras writes: > Hi Rainer, > > On Thu, Sep 3, 2015 at 11:24 AM, Rainer M Krug wrote: >> >> Hi >> >> is anything happening in regards to the travis-ci integration? I did not >> get any feedback or how I can submit it to the svn. > > Ideally open a

Re: [GRASS-dev] Travis-ci and tests of grass 7

2015-09-05 Thread Vaclav Petras
Hi Rainer, On Thu, Sep 3, 2015 at 11:24 AM, Rainer M Krug wrote: > > Hi > > is anything happening in regards to the travis-ci integration? I did not > get any feedback or how I can submit it to the svn. Ideally open a ticket a submit a diff. That's what I do (although I can

[GRASS-dev] Travis-ci and tests of grass 7

2015-09-03 Thread Rainer M Krug
Hi is anything happening in regards to the travis-ci integration? I did not get any feedback or how I can submit it to the svn. In regards to testing: I know about the python gunit tests [1]. Are there any other tests which should be included in the scripts? Should detailed results generated by