-
-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests fail with zlib-ng #1678
Comments
Oh, actually, it appears you don't even need to build from source, as wheels use system zlib, so a shorter reproducer:
|
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Jun 17, 2024
…pers#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Jun 17, 2024
…pers#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Jun 17, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Jun 17, 2024
…pers#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Jun 17, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Aug 19, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Sep 6, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Sep 6, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Sep 6, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Oct 12, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Oct 18, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Oct 18, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Oct 18, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
AdamWill
added a commit
to AdamWill/zarr-python
that referenced
this issue
Oct 20, 2024
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
dstansby
added a commit
that referenced
this issue
Jan 16, 2025
As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com> Co-authored-by: David Stansby <dstansby@gmail.com>
QuLogic
pushed a commit
to QuLogic/zarr
that referenced
this issue
Jan 21, 2025
…s#1678) As explained in the issue, zlib-ng produces different hex digests from original zlib. This adjusts the tests slightly to allow for this. Signed-off-by: Adam Williamson <awilliam@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Zarr version
2.16.1
Numcodecs version
0.12.1
Python Version
3.12
Operating System
Fedora Rawhide/40
Installation
from source
Description
Fedora 40 is transitioning to using zlib-ng; this provides an ABI-compatible replacement that is parallel and optimized for current processors. Unfortunately, it also produces results which may be different (but as I understand it, of similar compression ratio). This causes several tests to fail, as they compute the exact hex digest of the result.
I'm not sure if I should just start skipping these tests, or try and update them in some way.
Steps to reproduce
On a Fedora Rawhide or Fedora 40 container, install dependencies, then install zarr and run tests:
Additional output
Failing test output
The text was updated successfully, but these errors were encountered: