Hi, > Yes, what Dan said is true. > > After updating clang that false positive is gone and the build is > clean, but now a failure is accepted. Depending on useful it turns out > to be I might do some grep-foo to just throw the errors and summary in > the future.
I faced a similar issue with GDAL. The following might help to create a human friendly summary: - in https://github.com/OSGeo/gdal/blob/master/gdal/ci/travis/csa_part_1/install.sh#L14 ==> Using -o to output to a controled directory and -sarif for the json-based output format - https://github.com/OSGeo/gdal/blob/master/gdal/ci/travis/csa_common/script.sh To postprocess all files written in the output directory and give first a detailed output, but not necessarily easy to understand. And a final summary section that contains just the filename, line and warning message. You may need to edit line 10 to remove a few GDAL specific exclusions of false positives (or things in external code we don't/wan't to control) Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
