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 the tests be uploaded somewhere in case of an error? Or always? If yes, where? Also, should the same tests be done for other versions? Cheers, Rainer Rainer M Krug <rai...@krugs.de> writes: > Quick update: the tests are running, the forked github repo is > > https://github.com/rkrug/grass-ci > > and the travis-ci is here (the actually running one) > > https://travis-ci.org/rkrug/grass-ci/builds/77509876 > > It looks good now. > > Cheers, > > Rainer > > Rainer M Krug <rai...@krugs.de> writes: > >> Hi Ivan, Hi Markus, >> >> I have looked at the .travis.yml at >> [https://trac.osgeo.org/grass/browser/grass/trunk/.travis.ym]l >> and merged it with mine by >> >> 1) moving the sections of the .travis.yml fiole into scripts: >> >> - before_install :: .travis.$TRAVIS_OS_NAME.before_install.sh >> - install :: .travis.$TRAVIS_OS_NAME.install.sh >> - script :: .travis.$TRAVIS_OS_NAME.script.sh >> >> 2) using a travis multiple OS [http://docs.travis-ci.com/user/multi-os/] >> which sets the variable $TRAVIS_OS_NAME to "osx" or "linux" (hopefully >> "windows" in the future as well) >> >> So when testing on linux, the scripts with *.linux.*.sh are called, when >> testing osx the one=s with *.osx.*.sh get called >> >> 3) adding the different compiler to the matrix >> >> So I end up with three separate test scenarios: >> >> ,---- >> | - os: linux >> | language: c >> | compiler: gcc >> | >> | - os: linux >> | language: c >> | compiler: clang >> | >> | - os: osx >> | compiler: objective-c >> `---- >> >> I forked [https://github.com/GRASS-GIS/grass-ci] and am running the test >> at the moment - see [https://travis-ci.org/rkrug/grass-ci/builds/77484863] >> for the tests. >> >> They completed successful. >> >> There is still some fine tuning which could be done, especially with >> including of tests - which should not be to difficult. >> >> What would be the easiest to get the new files into the grass repo, id=f >> you are happy with it? >> >> Cheers, >> >> Rainer >> >> Markus Neteler <nete...@osgeo.org> writes: >> >>> Hi Ivan, >>> >>> I asked Rainer who is willing to contribute the MacOSX part (end of the >>> month). >>> >>> See below. >>> >>> Thanks, Rainer! >>> >>> Markus >>> >>> On Fri, Aug 14, 2015 at 10:09 AM, Rainer M Krug <r.m.k...@gmail.com> wrote: >>>> >>>> >>>> Envoyé de mon iPhone >>>> >>>>> Le 14 août 2015 à 09:45, Markus Neteler <nete...@osgeo.org> a écrit : >>>>> >>>>> Hi Rainer, >>>> >>>> Hi Markus, >>>> >>>>> >>>>> given your experience with homebrew, I wondered if you would be >>>>> willing to assist in setting up a Travis-CI instance for OSX here: >>>> >>>> Yes - That is my idea. To have a Travis-CI instance for all major OS >>>> should be the aim. >>>> >>>>> >>>>>> On Tue, Jul 21, 2015 at 11:52 AM, Ivan Minčík <ivan.min...@gmail.com> >>>>>> wrote: >>>>>> Hi all, >>>>>> we have just integrated Travis Continuous Integration system [1] to the >>>>>> GRASS source code. Every commit is now build in Travis [2] using gcc and >>>>>> clang. In case the build fails, error message should go to GRASS-dev >>>>>> list. >>>>>> >>>>>> >>>>>> 1 - https://trac.osgeo.org/grass/browser/grass/trunk/.travis.yml >>>>>> 2 - https://travis-ci.org/GRASS-GIS/grass-ci >>>>>> >>>>>> -- >>>>>> Ivan Minčík >>>>>> ivan.min...@gmail.com GPG: 0x79529A1E >>>>>> http://imincik.github.io/0x79529A1E.key >>>>>> ivan.min...@gista.sk GPG: 0xD714B02C >>>>>> http://imincik.github.io/0xD714B02C.key >>>>> >>>>> >>>>> This works well for Linux now. >>>>> Reading this email on qgis-psc, I got the impression that it is >>>>> "simple" also for OSX: >>>>> >>>>> >>>>>> On Fri, Aug 14, 2015 at 7:31 AM, Nyall Dawson <nyall.daw...@gmail.com> >>>>>> wrote: >>>>>>> On 13 August 2015 at 04:32, Tim Sutton <t...@qgis.org> wrote: >>>>>>> Awesome stuff Nyall - can you give any notes on what specifically you >>>>>>> had to do to enable OS X testing? >>>>>> >>>>>> Not much really... all the ground work was already in place and were >>>>>> just waiting on Travis to open up multi OS builds again. Whoever setup >>>>>> the homebrew install package (Larry?) made it super easy to install >>>>>> the dependencies, and we already had 99% of the tests passing without >>>>>> error on OSX. Michael Kirk had also already given this a shot so I was >>>>>> able to borrow parts of his attempts which also helped a lot. >>>>>> >>>>>> Nyall >>>>>> _______________________________________________ >>>>>> Qgis-psc mailing list >>>>>> qgis-...@lists.osgeo.org >>>>>> http://lists.osgeo.org/mailman/listinfo/qgis-psc >>>>> >>>>> >>>>> Ivan does not have time for it but he's maybe willing to tell you how >>>>> to log into the system. >>>>> >>>>> What do you think? >>>> >>>> As you probably know, I have a running Travis-ci for OS X and it could be >>>> integrated there. >>>> >>>> The homebrew recipe needs some alignment in this case (and possibly >>>> a new more "official" home) but that should be relatively straight >>>> forward. >>>> >>>> At the moment I am on holiday but should be able to look at it in the last >>>> week of August. >>>> >>>> Please remind me of you don't hear from me by end of August. >>>> >>>> Cheers and thanks for the offer, >>>> >>>> Rainer >>>> >>>>> >>>>> Markus Footnotes: [1] https://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982
signature.asc
Description: PGP signature
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
