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.
On Tue, Mar 10, 2020 at 2:35 AM Daniel Baston <dbas...@gmail.com> wrote: > > Yeah, the reporting is pretty bad. If you search the log for "warning" you > will find the cause: > > https://travis-ci.com/libgeos/geos/jobs/266448653#L1082 > > which is a false positive. The build shows as failed since it's from 3 months > ago; Raul has since changed the configuration so that scan-build reports but > does not fail the build. > > Dan > > On Mon, Mar 9, 2020 at 6:20 PM Paul Ramsey <pram...@cleverelephant.ca> wrote: >> >> I see “scan-build” has entered the CI zoo on master, and I see it has borked >> a PR, but I cannot see *why* it has borked it… >> >> Here’s the PR >> >> https://github.com/libgeos/geos/pull/252 >> >> Here’s the build >> >> https://travis-ci.com/libgeos/geos/jobs/266448653 >> >> This is not actionable information, how is someone who has tripped this wire >> supposed to respond? >> >> P. >> _______________________________________________ >> geos-devel mailing list >> geos-devel@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/geos-devel > > _______________________________________________ > geos-devel mailing list > geos-devel@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/geos-devel -- Raúl Marín Rodríguez carto.com _______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
