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 wr
On Mon, Mar 09, 2020 at 01:51:30PM -0700, Paul Ramsey wrote:
> I’d like to cut a 3.8.1 release ASAP, probably tomorrow morning.
Yes please, thank you !
--strk;
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listin
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 GDA
#1020: Performance regression in GEOSBuffer
+--
Reporter: dbaston | Owner: geos-devel@…
Type: defect | Status: new
Priority: major | Milestone:
Component: Default |Version: 3.8.0
Severity: Unassigned |
#1020: Performance regression in GEOSBuffer
+---
Reporter: dbaston | Owner: geos-devel@…
Type: defect | Status: closed
Priority: major | Milestone:
Component: Default | Version: 3.8.0
Severity: Unass
The latest patch release of GEOS stable branch is out.
We recommend you upgrade as soon as possible, there is a fixed bug that can be
exercised to crash backend services.
There is also a fixed performance issue relative to the 3.7 branch.
http://download.osgeo.org/geos/geos-3.8.1.tar.bz2
Improv
