On Tue, Aug 4, 2015 at 2:14 AM, Pietro <peter.z...@gmail.com> wrote:
>
> I've stopped to go on with the syncronization of my local changes and
> trunk since I noticed that from the 27th of July the tests are not
> running anymore:
>
> http://fatra.cnr.ncsu.edu/grassgistests/summary_report/nc/index.html
>
> I don't understand why, but I have the suspect that the recent changes
> done in lib/init/grass.py and gunittest:
>
> https://trac.osgeo.org/grass/changeset/65780
> https://trac.osgeo.org/grass/changeset/65782
>
> have broken something.
>
> I will not go further on the development of python2/python3 until this
> issue will be fix.

The issue was caused by missing g.region call in one of the tests [1, 2].

However, now I see at least 3 tests which were not failing before [3, 4,
5]. It seems like a trivial issue caused by some automatic changes (percent
operator is missing). This issue should be visible on any machine.

Also the error messages seems to be inappropriate. This should just fail
and not report an error (perhaps an except statement without an exception
specified?). And also the formatting is wrong since <> is missing around
the vector map name. Perhaps all three messages should be the same.

To run just one selected test use, for example:

cd scripts/v.what.strds/testsuite
python test_what_strds.py TestWhatStrds.test_output

Vaclav

[1] https://lists.osgeo.org/pipermail/grass-dev/2015-May/075025.html
[2] https://lists.osgeo.org/pipermail/grass-dev/2015-August/075900.html
[3]
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-08-04-16-20/report_for_nc_basic_spm_grass7_nc/temporal/t.vect.observe.strds/test.t.vect.observe.strds.relative/index.html
[4]
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-08-04-16-20/report_for_nc_basic_spm_grass7_nc/temporal/t.vect.observe.strds/test.t.vect.observe.strds/index.html
[5]
http://fatra.cnr.ncsu.edu/grassgistests/reports_for_date-2015-08-04-16-20/report_for_nc_basic_spm_grass7_nc/scripts/v.what.strds/test_what_strds/index.html
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Reply via email to