l Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
ok, I've looked a bit at the code
So I believe the issue is that
- https://github.com/OSGeo/gdal/blob/master/apps/test_ogrsf.cpp#L1064 forms a
"/foo/test.pol" filename for the miramon driver and call Crea
IMkdir()
*Perhaps if the destination folder doesn’t exist I should NOT create
it and return a FAILURE?*
*De:*Abel Pau
*Enviado el:* dimecres, 6 de març de 2024 16:24
*Para:* Abel Pau ; Even Rouault
; gdal-dev@lists.osgeo.org
*Asunto:* RE: [gdal-dev] Testing the driver
Hi,
It seems nothing chang
ow to delete that? I
don’t use anymore: VSIMkdirRecursive(). I use VSIMkdir()
Perhaps if the destination folder doesn’t exist I should NOT create it and
return a FAILURE?
De: Abel Pau
Enviado el: dimecres, 6 de març de 2024 16:24
Para: Abel Pau ; Even Rouault
; gdal-dev@lists.osgeo.org
Asunto: RE
:* gdal-dev *En nombre de *Abel Pau
> via gdal-dev
> *Enviado el:* dijous, 7 de març de 2024 23:42
> *Para:* Even Rouault ; Andrew C Aitchison <
> and...@aitchison.me.uk>; Daniel Evans
> *CC:* 'gdal-dev@lists.osgeo.org' (gdal-dev@lists.osgeo.org) <
> gdal-de
via
gdal-dev
Enviado el: dijous, 7 de març de 2024 23:42
Para: Even Rouault ; Andrew C Aitchison
; Daniel Evans
CC: 'gdal-dev@lists.osgeo.org' (gdal-dev@lists.osgeo.org)
Asunto: Re: [gdal-dev] Testing the driver
Hi,
It’s in debug mode, yes, as you suggested.
yes, it crashes in th
Re: [gdal-dev] Testing the driver
At #10 we can see the variable nNum set to a non-sense megabignumber.
Is it on a -DCMAKE_BUILD_TYPE=Debug build ? Otherwise stack traces and variable
content in the debugger might look like garbage because of optimizations.
If it is a debug build, then ther
At #10 we can see the variable nNum set to a non-sense megabignumber.
Is it on a -DCMAKE_BUILD_TYPE=Debug build ? Otherwise stack traces and
variable content in the debugger might look like garbage because of
optimizations.
If it is a debug build, then there's likely some memory corruption o
-Mensaje original-
De: Andrew C Aitchison
Enviado el: dijous, 7 de març de 2024 1:01
Para: Daniel Evans
CC: Abel Pau ; 'gdal-dev@lists.osgeo.org'
(gdal-dev@lists.osgeo.org)
Asunto: Re: [gdal-dev] Testing the driver
On Wed, 6 Mar 2024, Daniel Evans via gdal-dev wrote:
>
On Wed, 6 Mar 2024, Daniel Evans via gdal-dev wrote:
Is it worth moving this in-depth discussion to a PR or similar for the new
driver?
My thinking is that a lengthy discussion on memory leak detection
techniques in C++, how to run tests in Python, etc., aren't topics relevant
to most GDAL mail
2
> *Para:* Abel Pau ; gdal-dev@lists.osgeo.org
> *Asunto:* Re: [gdal-dev] Testing the driver
>
>
>
> PYTHONMALLOC=malloc gdb --args python3 -m pytest
> autotest/ogr/ogr_miramon_vector.py
>
> PYTHONMALLOC=malloc valgrind python3 -m pytest
> autotest/ogr/ogr_miramon_vect
I was using ubuntu 20.04 and it doesn’t work there.
Trying to install 22.04 but I have some issues (again).
De: Even Rouault
Enviado el: dimecres, 6 de març de 2024 17:12
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
PYTHONMALLOC=malloc gdb --args
uot;/usr/local/lib/python3.8/dist-packages/pluggy/_hooks.py", line
501 in __call__
File "/usr/local/lib/python3.8/dist-packages/_pytest/main.py", line
327 in _main
File "/usr/local/lib/python3.8/dist-packages/_pytest/main.py", line
273 in wrap_session
File "/us
com/AbelPau/gdal/actions/runs/8172351502/job/22342474513>
De: gdal-dev En nombre de Abel Pau via
gdal-dev
Enviado el: dimecres, 6 de març de 2024 13:52
Para: Even Rouault ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
Ok, I ‘ve changed that. Let’s see if it’s the p
"/usr/local/lib/python3.8/dist-packages/_pytest/runner.py", line 223 in
call_and_report
File "/usr/local/lib/python3.8/dist-packages/_pytest/runner.py", line 134 in
runtestprotocol
File "/usr/local/lib/python3.8/dist-packages/_pytest/runner.py", line 115 in
pyt
ic_test.py
✓✓
100% ██
Results (5.98s):
66 passed
De: Even Rouault
Enviado el: dimecres, 6 de març de 2024 13:09
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
Hi,
I don't see anything wrong. I've tried that on m
Ok, I ‘ve changed that. Let’s see if it’s the problem.
It’s all so delicate :)
Thanks again!
De: Even Rouault
Enviado el: dimecres, 6 de març de 2024 13:36
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
Le 06/03/2024 à 13:14, Abel Pau a écrit :
Hi Even,
I
Para:* Abel Pau ; gdal-dev@lists.osgeo.org
*Asunto:* Re: [gdal-dev] Testing the driver
Hi,
I don't see anything wrong. I've tried that on my native Linux build
and the test_ogr_miramon_vector_1() is found. Does "pytest
autotest/ogr/ogr_basic_test.py" work?*
Note: you don&#x
e_133():
Do you know what it can be?
De: Even Rouault
Enviado el: dimecres, 6 de març de 2024 13:09
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
Hi,
I don't see anything wrong. I've tried that on my native Linux build and the
test_ogr_miramon
t;) == "2"
ds = None
except Exception as e:
pytest.fail(f"Test failed with exception: {e}")
*De:*Even Rouault
*Enviado el:* divendres, 9 de febrer de 2024 11:48
*Para:* Abel Pau ; gdal-dev@lists.osgeo.org
*Asunto:* Re: [gdal-dev] Testing the driver
Abel,
Le 09/02/2024 à
pytest.fail(f"Test failed with exception: {e}")
De: Even Rouault
Enviado el: divendres, 9 de febrer de 2024 11:48
Para: Abel Pau ; gdal-dev@lists.osgeo.org
Asunto: Re: [gdal-dev] Testing the driver
Abel,
Le 09/02/2024 à 10:55, Abel Pau via gdal-dev a écrit :
Hi,
I am at the l
On Sun, 18 Feb 2024, Even Rouault wrote:
Le 10/02/2024 à 18:34, Andrew C Aitchison via gdal-dev a écrit :
On Sat, 10 Feb 2024, Even Rouault via gdal-dev wrote:
To test your own development, you may have a more pleasant experience by
directly running just the tests for your driver with somethi
Le 10/02/2024 à 18:34, Andrew C Aitchison via gdal-dev a écrit :
On Sat, 10 Feb 2024, Even Rouault via gdal-dev wrote:
To test your own development, you may have a more pleasant
experience by directly running just the tests for your driver with
something like "pytest autotest/ogr/ogr_miramo
On Sat, 10 Feb 2024, Even Rouault via gdal-dev wrote:
To test your own development, you may have a more pleasant experience by
directly running just the tests for your driver with something like "pytest
autotest/ogr/ogr_miramon.py" (be careful on Windows, the content of
$build_dir/autotest
To test your own development, you may have a more pleasant experience
by directly running just the tests for your driver with something like
"pytest autotest/ogr/ogr_miramon.py" (be careful on Windows, the
content of $build_dir/autotest is copied from $source_dir/autotest
each time "cmake" i
Abel,
Le 09/02/2024 à 10:55, Abel Pau via gdal-dev a écrit :
Hi,
I am at the lasts steps before pulling a request about the MiraMon
driver.
I need to write some documentation and formalize the tests.
After that, I’ll do the pull request to github.
I'd suggest first before issuing the pull
Hi,
I am at the lasts steps before pulling a request about the MiraMon driver.
I need to write some documentation and formalize the tests.
After that, I'll do the pull request to github.
I am a little confused about the testing. I can use pytest or ctest, right?
Which is the favourite? Are there
26 matches
Mail list logo
