[gdal-dev] Alpine, gcc 32-bit in Linux Build Actions
Abel Pau
a.pau at creaf.uab.cat
Fri Mar 1 02:29:04 PST 2024
Hi,
yesterday I updated my personal branch (soon I'll do a pull request) but before as Even suggested I'm trying to make green al Actions.
The only problem I have now is at some points on tests...
But I am missing something because I there are things I don't understand well.
Can anyone give me some new information to clarify myself?
test_ogr_basic_10
It's this INFO message (that other drivers also give) a problem?
INFO: MiraMonVector: Creation of /foo\test.pol should have failed.
This message also appears in some other drivers.
INFO: MiraMonVector: CreateFeature() at line 780 succeeded but failed to assign FID to feature.
Al tests in Linux Builds<https://github.com/AbelPau/gdal/actions/runs/8101809119> (in Actions) are OK except Alpine, gcc 32-bit
MiraMonVector driver (the one I am testing) seems to be OK.
gcore/test_driver_metadata.py::test_metadata_dcap_yes[MiraMonVector] PASSED [ 38%]
gcore/test_driver_metadata.py::test_metadata_openoptionlist[MiraMonVector] PASSED [ 40%]
gcore/test_driver_metadata.py::test_metadata_creationoptionslist[MiraMonVector] PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_layer_creationoptionslist[MiraMonVector] PASSED [ 42%]
gcore/test_driver_metadata.py::test_metadata_creation_field_datatypes[MiraMonVector] PASSED [ 44%]
gcore/test_driver_metadata.py::test_metadata_creation_sub_field_datatypes[MiraMonVector] PASSED [ 46%]
gcore/test_driver_metadata.py::test_metadata_alter_geom_field_defn_flags[MiraMonVector] PASSED [ 47%]
gcore/test_driver_metadata.py::test_metadata_alter_field_defn_flags[MiraMonVector] PASSED [ 48%]
gcore/test_driver_metadata.py::test_metadata_creation_field_defn_flags[MiraMonVector] PASSED [ 48%]
But
2024-02-29T20:01:51.4283306Z ogr/ogr_basic_test.py::test_ogr_basic_10 FAILED [ 1%]
=================================== FAILURES ===================================
______________________________ test_ogr_basic_10 _______________________________
Al some point: ERROR ret code = -6
But no more clues why.
Anyone can tell me how to explore this error?
I debugged this test in windows but all seems correct.
The program '[15680] test_ogrsf.exe' has exited with code 0 (0x0).
I finally installed a linux ubuntu:22.04 in a docker and I can do some things related to tests.
When I do
python3 -m pytest -vv -p no:sugar --color=no ogr/ogr_basic_test.py::test_ogr_basic_10
After a while this error appears.
So, why?
E INFO: OpenFileGDB: CreateFeature() at line 837 failed but without explicit error.
E INFO: TestCreate(DXF).
E INFO: DXF: Creation of /foo/test.
E ERROR ret code = -9
E assert 'ERROR' not in 'INFO: TestCreate(PCIDSK).\nINFO: PCIDSK: Creation of /foo/test.pix should have failed.\nINFO: TestCreate(netCDF).\nINFO: netCDF: Creation of /foo/test.nc should have failed.\nINFO: netCDF: Creation of /vsimem/test33.n....
Abel Pau Garcia
GIS developer
[https://www.creaf.cat/sites/default/files/creaf-signature.png]
a.pau at creaf.uab.cat<mailto:a.pau at creaf.uab.cat>
Let's chat on Teams!<https://teams.microsoft.com/l/chat/0/0?users=a.pau@creaf.uab.cat>
Tel. +34 934814277
[https://www.creaf.cat/sites/default/files/so-en-signature.png]
[https://www.creaf.cat/sites/default/files/twitter-icon-signature.png]<https://twitter.com/CREAF_ecologia>[https://www.creaf.cat/sites/default/files/linkedin-icon-signature.png]<https://www.linkedin.com/company/1363052?trk=tyah&trkInfo=clickedVertical:company,clickedEntityId:1363052,idx:2-1-2,tarId:1465807877789,tas:creaf>[https://www.creaf.cat/sites/default/files/youtube-icon-signature.png]<https://www.youtube.com/c/creafecologia>[https://www.creaf.cat/sites/default/files/instagram-icon-signature.png]<https://www.instagram.com/CREAF_ecologia/>
www.creaf.cat<http://www.creaf.cat> | http://blog.creaf.cat
[https://www.creaf.cat/sites/default/files/uab_logo_signatura.png]
CREAF. Campus UAB. Edifici C. 08193 Bellaterra (Barcelona)
Before printing this electronic message, think about the environment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3657 bytes
Desc: image001.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2547 bytes
Desc: image002.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 505 bytes
Desc: image003.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 446 bytes
Desc: image004.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 553 bytes
Desc: image005.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 582 bytes
Desc: image006.png
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 2208 bytes
Desc: image007.jpg
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 1111 bytes
Desc: image008.jpg
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240301/d0eed343/attachment-0003.jpg>
More information about the gdal-dev
mailing list