Hello Markus, as most of errors reported are legit, some of them are useless at the current philosophy of GRASS GIS. We are OK with small memory leaks, as modules are intended to be short running and then memory is reclaimed by the OS (this is faster than freeing it before exit). Of course, this would not be OK for long-running apps. Unless we change our approach, resource leaks are just a noise.
I would vote against integrating Coverty scan into CI — just to keep noise level down. It is useless to get regular reports if we do not plan (lack of manpower) to react to them. Just my 0.02 cents, Māris. pirmd., 2020. g. 3. febr., plkst. 21:50 — lietotājs Markus Neteler (<nete...@osgeo.org>) rakstīja: > > Hi devs, > > I have re-run the coverity scan on master, results below. > > There is also the option of Travis integration which might be a good idea. > Anyone to support this? > > Markus > > _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
