[GRASS-dev] [GRASS GIS] #3771: Run tests on Travis

[GRASS GIS]

#3771: Run tests on Travis
--------------------------+-------------------------
  Reporter:  pmav99       |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:
 Component:  Tests        |    Version:  svn-trunk
Resolution:               |   Keywords:
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------

Comment (by sbl):

 In principle, fully agreed on all points regarding tests.

 Just to add some history. Python 3 support was to a significant amount
 worked on in a GSoC project in 2018
 (https://lists.osgeo.org/pipermail/soc/2018-August/004186.html), although
 that was a big step forward, open issues remained. And after that project
 finished, a decision had to be made to either merge the unfinished code
 (leading to failing tests) or wait and risk that merging the code later
 would become harder and harder. Decision was made for the latter (see
 r73229).

 Comparing test results before and after this commit (2018-09-02 vs.
 2018-09-03) can give an idea about failing tests because of introduction
 of Python 3 vs. other failures:

   *
 http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2018-09-02-07-00/report_for_nc_basic_spm_grass7_nc/testsuites.html
   *
 http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2018-09-03-07-00/report_for_empty_xy_all/testsuites.html


 So, making tests pass is a matter of resources (time) I guess, and I am
 sure contributions are more than welcome. The question is, what is the
 best way forward. Suggestions fromm my side would be to:

   * **Make the test suite and test coverage a topic for a community
 sprint**. If those who know the test suite well could help others (like
 me) to improve their procedures that would be really cool and appreciated.
   * **Prioritize move to git** if that helps people like you, Panos, to
 contribute and help with Python 3 support (which is supposed to be a focus
 for the 7.8 release) Really good to see your recent activity here, BTW!
   * **Crack down on the other 10%** of failing test (fix or deactivate
 temporarily if necessary as you suggest)

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3771#comment:6>
GRASS GIS <https://grass.osgeo.org>