Re: [gdal-dev] Test Failure Question
On Thu, Jan 9, 2020 at 3:18 PM Even Rouault wrote: > Andrew, > > > Any ideas what might be going on or what I might look for to fix? > > Did you build GDAL yourself ? Check if you built against internal libtiff > or > not ? If you built against internal libtiff, make sure to use > --with-rename-internal-libtiff-symbols I didn't set any special options in configure when I built. What happens in this case? I don't see libtiff in the set of libraries to be linked. Is it dlopen'ed? -- Andrew Bell andrew.bell...@gmail.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Test Failure Question
Andrew, > Any ideas what might be going on or what I might look for to fix? Did you build GDAL yourself ? Check if you built against internal libtiff or not ? If you built against internal libtiff, make sure to use --with-rename-internal-libtiff-symbols to avoid any potential symbol clash with an external libtiff that might be indirectly linked. Similarly for libgeotiff Otherwise Valgrind is one of my best friends in such situations Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Test Failure Question
Hi Andrew,
Running the test under lldb will give you some leads. Within your activated
environment, so that "python" is the correct one:
$ lldb python
(lldb) run -m pytest /Users/acbell/gdal/autotest/gcore/tiff_ovr.py
On Thu, Jan 9, 2020 at 11:48 AM Andrew Bell
wrote:
> Hi,
>
> I'm getting an abort when I run autotest on OSX:
>
> gcore/tiff_ovr.py
> ..Fatal
> Python error: Aborted
>
> Current thread 0x7fff9465d380 (most recent call first):
> File "/Users/acbell/gdal/autotest/gcore/tiff_ovr.py", line 1364 in
> test_tiff_ovr_43
> File
> "/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/_pytest/python.py",
> line 166 in pytest_pyfunc_call
> File
> "/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/callers.py",
> line 187 in _multicall
> File
> "/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/manager.py",
> line 84 in
> File
> "/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/manager.py",
> line 93 in _hookexec
> ...
>
> Line 1364 is:
>
> ds = gdaltest.tiff_drv.Create('tmp/ovr43.tif', 16, 16, 1, gdal.GDT_UInt16)
>
> Any ideas what might be going on or what I might look for to fix?
>
> Thanks,
>
> --
> Andrew Bell
> andrew.bell...@gmail.com
> ___
> gdal-dev mailing list
> gdal-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
--
Sean Gillies
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
[gdal-dev] Test Failure Question
Hi,
I'm getting an abort when I run autotest on OSX:
gcore/tiff_ovr.py
..Fatal
Python error: Aborted
Current thread 0x7fff9465d380 (most recent call first):
File "/Users/acbell/gdal/autotest/gcore/tiff_ovr.py", line 1364 in
test_tiff_ovr_43
File
"/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/_pytest/python.py",
line 166 in pytest_pyfunc_call
File
"/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/callers.py",
line 187 in _multicall
File
"/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/manager.py",
line 84 in
File
"/Users/acbell/miniconda3/envs/gdaldev/lib/python3.8/site-packages/pluggy/manager.py",
line 93 in _hookexec
...
Line 1364 is:
ds = gdaltest.tiff_drv.Create('tmp/ovr43.tif', 16, 16, 1, gdal.GDT_UInt16)
Any ideas what might be going on or what I might look for to fix?
Thanks,
--
Andrew Bell
andrew.bell...@gmail.com
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] Fwd: Re: [Projects] OSGeo Budget 2020
Hi, no feedback on this ? If not, I'll motion shortly that we request the default 2000 USD budget with a presumed use of supporting attendance at code sprints & conferences. Even > Hi, > > I had apparently missed the initial email for this request to ask for a 2020 > budget. Do we have specific needs ? > > After short discussion with the OSGeo treasurer, it appears that the cost > for the extended Travis-CI support that were covered through GDAL budget in > 2018 and 2019 will go to a general OSGeo budget line in 2020 > (infrastructure or so), as they are shared with other projects like PROJ. > > Even > > -- Forwarded Message -- > > Subject: Re: [Projects] OSGeo Budget 2020 > Date: lundi 23 décembre 2019, 20:35:20 CET > From: Angelos Tzotsos > To: proje...@lists.osgeo.org > CC: OSGeo Discussions , OSGeo Board > > > Hi all, > > Please submit your budget requests by Dec 30th so we can start drafting > the 2020 budget. > > Happy holidays, > Angelos > > On 12/9/19 9:38 PM, Angelos Tzotsos wrote: > > Dear OSGeo project members and committees, > > > > Over the previous years, OSGeo has been proud to support a growing > > number of project events, such as code sprints, developer meetings, > > and user conferences. > > > > OSGeo is reaching out to all committees, including project steering > > committees, to help plan our budget for 2020. > > > > As in last year, the board is discussing about assigning a starting > > budget of 2000$ to all graduated projects who have reported to the > > board the last 12 months (e.g. during the AGM or directly to a board > > meeting). > > > > For projects with more of a plan (to pursue a specific goal) projects > > are welcome to send a more detailed request for approval (see detailed > > budget requests from 2019 e.g. > > https://wiki.osgeo.org/wiki/GvSIG_Budget_2019) > > > > A good idea is to focus on OSGeo participation, for example attending > > the AGM or OSGeo code sprint. Also keep in mind OSGeo goals as an > > organization, (e.g. interoperability goal: CITE compliance or > > participation developing new standards) > > > > We would like to ask you to help us with budget proposals to assist > > your project. This will help us set aside a realistic amount of funding. > > > > Please add your project info to the budget draft at: > > > > https://wiki.osgeo.org/wiki/OSGeo_Budget_2020 > > > > ideally by Dec 30 ahead of our next board meeting. > > > > When making a budget request please keep in mind the vision and goals > > of our foundation, along with any obligations you wish to meet. > > > > Thank you. > > > > On behalf of the OSGeo Board, > > > > Angelos -- Spatialys - Geospatial professional services http://www.spatialys.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
