Issue #774: Fix assert_equal_content in test_rasterio_ascii #775
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #774
Description
Build in #760 fails for test_rasterio_ascii
test_rasterio_asciidoesn't work for GDAL 3.8.3 compared to 3.7.3.Previously it was tested if files are exactly identical. This defeats the purpose, more important is that GDAL can read the file and interprets the file equal as if it were written with GDAL. Replacing
assert_equal_contentwith the changes fixes things.Checklist
Issue #nr, e.g.Issue #737