<div dir="ltr">Hi all,<br><br>as reported earlier [1, 2] t.connect test test_distr_tgis_db_raster.py [3] in Piemonte Location [4] takes 3.5 hours to execute [5]. This is happening constantly for a long time already [6] but it was not happening at the very beginning [7].<br><br>Now I realized (the hard way) that the test was creating 40 GB of data (mostly null files). Which explains why it took so long and why the tests were broken (no space left on the device). The reason was forgotten call to g.region before creation of the test data. I fixed that in r65836 [8].<br><br>Tests on my server are now running again [9]. You can run them on your machine with your data in various ways [10] including:<br><br>    cd /grass/source/code/root<br>    ./bin.../grass71 ~/grassdata/your_location_name/PERMANENT/ \<br>        --exec python -m grass.gunittest.main \<br>        --location your_location_name --location-type nc<br><br>Vaclav<br><br><br>[1] <a href="https://lists.osgeo.org/pipermail/grass-dev/2015-May/075025.html">https://lists.osgeo.org/pipermail/grass-dev/2015-May/075025.html</a><br>[2] <a href="http://permalink.gmane.org/gmane.comp.gis.grass.devel/64361">http://permalink.gmane.org/gmane.comp.gis.grass.devel/64361</a><br>[3] <a href="http://trac.osgeo.org/grass/browser/grass/trunk/temporal/t.connect/testsuite/test_distr_tgis_db_raster.py">http://trac.osgeo.org/grass/browser/grass/trunk/temporal/t.connect/testsuite/test_distr_tgis_db_raster.py</a><br>[4] <a href="http://grass.osgeo.org/download/sample-data/">http://grass.osgeo.org/download/sample-data/</a><br>[5] <a href="http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-07-27-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html">http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-07-27-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html</a><br>[6] <a href="http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-09-18-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html">http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-09-18-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html</a><br>[7] <a href="http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-09-17-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html">http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-09-17-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html</a><br>[8] <a href="https://trac.osgeo.org/grass/changeset/65836">https://trac.osgeo.org/grass/changeset/65836</a><br>[9] <a href="http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/index.html">http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/index.html</a><br>[10] <a href="http://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html#running-tests-report">http://grass.osgeo.org/grass71/manuals/libpython/gunittest_running_tests.html#running-tests-report</a><br></div>