Hi, when I run t.connect test test_distr_tgis_db_raster.py [0] in Piemonte Location [1], it takes 3.5 hours to complete [2]. This is happening constantly for a long time already [3]. There is nothing in the outputs which would indicate anything like this. Any ideas?
In case you wonder how different data influence the time, then you can see run in NC SPM Location [4] and in an empty XY Location [5]. Also, similar tests for 3D raster and vector data are fine [6, 7]. Is somebody able to reproduce that behavior or determine why it is happening? Thanks, Vaclav [0] http://trac.osgeo.org/grass/browser/grass/trunk/temporal/t.connect/testsuite/test_distr_tgis_db_raster.py [1] http://grass.osgeo.org/download/sample-data/ [2] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-05-11-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html [3] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2014-10-02-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster/index.html [4] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-05-11-07-00/report_for_nc_spm_08_grass7_nc/temporal/t.connect/test_distr_tgis_db_raster/index.html [5] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-05-11-07-00/report_for_empty_xy_all/temporal/t.connect/test_distr_tgis_db_raster/index.html [6] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-05-11-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_raster3d/index.html [7] http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-05-11-07-00/report_for_piemonte_utm32_wgs84_grass7_stdmaps/temporal/t.connect/test_distr_tgis_db_vector/index.html
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
