See also: https://github.com/OSGeo/grass-addons/pull/488
That does not really solve the issue at hand. Unstable tests seem very unfortunate to me. But the PR contributes to improved addon testing and increases success rate.... Cheers Stefan From: grass-dev <grass-dev-boun...@lists.osgeo.org> On Behalf Of Vaclav Petras Sent: onsdag 24. mars 2021 02:15 To: Markus Neteler <nete...@osgeo.org> Cc: GRASS developers list <grass-dev@lists.osgeo.org> Subject: Re: [GRASS-dev] Failing addon releasebranch_7_8 (Python 3.6) pipeline On Mon, Mar 22, 2021 at 7:39 AM Markus Neteler <nete...@osgeo.org<mailto:nete...@osgeo.org>> wrote: Executing <python3 -m grass.gunittest.main --grassdata /home/runner --location nc_spm_full_v2alpha2 --location-type nc --min-success 60> ... generate_manpage_images from ./vector/v.stream.order failed test_stream_order from ./vector/v.stream.order failed (2 tests failed) test_pygbif_import from ./vector/v.in.pygbif failed (3 tests failed) test_v_db_pyupdate from ./vector/v.db.pyupdate failed (2 tests failed) r3_forestfrag_trivial from ./raster3d/r3.forestfrag failed (1 test failed) test_whatcsv from ./temporal/t.rast.whatcsv failed (1 test failed) test_whataggr from ./temporal/t.rast.what.aggr failed (6 tests failed) test_gpot from ./raster/r.green/r.green.gshp/libgshp failed test_numbers from ./raster/r.sample.category failed r_extract_test from ./raster/r.extract failed (2 tests failed) r_object_geometry_test from ./raster/r.object.geometry failed (2 tests failed) test_base_resolution from ./raster/r.in.pdal failed r_forestfrag_trivial from ./raster/r.forestfrag failed (1 test failed) r_forestfrag_xy from ./raster/r.forestfrag failed (1 test failed) test_append from ./raster/r.learn.ml2 failed Looking at all commits [1], it fails only sometimes although it seems really only in the releasebranch_7_8 (Python 3.6) combo. By comparing the lists of failing tests in Meld, I identified that the fluctuating test is r_forestfrag_xy from ./raster/r.forestfrag failed. Resolving that, or fixing any other failing test (test file to be exact) will stabilize the success rate above 60% and resolve this issue without lowering the rate or introducing separate success rates for each combo at this point. Does anyone know why it fails in the releasebranch_7_8 (Python 3.6) pipeline but works in releasebranch_7_8 (Python 3.8)? This would be good of course good to investigate... [1] https://github.com/OSGeo/grass-addons/commits/master<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOSGeo%2Fgrass-addons%2Fcommits%2Fmaster&data=04%7C01%7C%7C5668676861a8424f7d2e08d8ee6258cb%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C637521453477292909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=va%2FJ88vy182%2B%2BNlgwfXh6aF5ZylwOZZC7Q8H%2F6i3enY%3D&reserved=0>
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
