bump build, add test_read_compdcs to skipped tests

[akrherz]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

Would like to see what a simple rebuild does

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[akrherz]

@conda-forge-admin please rerender

[akrherz]

OK, same error as #274

ImportError: libabsl_cord.so.2301.0.0: cannot open shared object file: No such file or directory

[akrherz]

@conda-forge-admin please restart ci

[akrherz]

Oh dear, now we have a segfault with the new tiledb build in play

tests/test_crs.py::test_read_epsg PASSED                                 [  5%]
Fatal Python error: Segmentation fault

[akrherz]

Another tiledb build has landed, so lets try once more!

@conda-forge-admin please restart ci

[akrherz]

@conda-forge/rasterio , this PR is now green. It does add test_read_compdcs to the skip list as it is segfaulting, but I have not much idea on how to debug it :(

[weiji14]

@conda-forge/rasterio , this PR is now green. It does add test_read_compdcs to the skip list as it is segfaulting, but I have not much idea on how to debug it :(

Looks like the same segfault seen at https://github.com/rasterio/rasterio-wheels/pull/110 and mentioned at https://github.com/rasterio/rasterio-wheels/issues/109#issuecomment-1724693267? Should we wait for upstream rasterio to resolve things, or just skip the test for now?

[sgillies]

@akrherz I'm not glad about the segfault, but am relieved it's not just me! I wonder WTF is going on. For what it's worth, I'm seeing the same segfault with GDAL 3.6.4 with no change to my build configuration from the one I used to release 1.3.8. I suspect some unspecified piece of my build system has changed in an incompatible way. CMake version? Cython? The CI runner images (they've all changed since my last wheel builds)? I dunno.

[akrherz]

Eh, I'm not seeing much strong opinions, so will merge this so to get the proj 9.3 migration done. Will ensure first we get another green build.

@conda-forge-admin please rerender

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[sgillies]

@akrherz skipping a crashing test seems risky?

[akrherz]

:wave: @sgillies , you are correct, but I don't believe there is bandwidth here to resolve these types of failures that seem transient. Given that it crept in without any rasterio code changes furthers my point. And lamely, carrying a list of skipped tests for conda-forge packages is more the norm than the exception. We also have a practical matter of needing to clear migrations so to keep dependency logjams from becoming too severe. It would also help if conda-forge had more sharp cookies instead of dull/blunt hammers like me :(

[snowman2]

Oh dear, now we have a segfault with the new tiledb build in play

tests/test_crs.py::test_read_epsg PASSED                                 [  5%]
Fatal Python error: Segmentation fault

This was addressed here: https://github.com/rasterio/rasterio/pull/2875

It is slated for version 1.4.