Skip to content

BUG: Fix discovered MachAr (still used within valgrind) #21815

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

Merged
merged 1 commit into from
Jun 26, 2022

Conversation

seberg
Copy link
Member

@seberg seberg commented Jun 21, 2022

This fixes the missing attributes. I tested the warning and fix
on valgrind itself.
These attributes were added in gh-18536 but the fallback path was
not checked there.

Replaces gh-21813, although something more like it may make sense
if it allows us to just delete MachAr completely.

This fixes the missing attributes.  I tested the warning and fix
on valgrind itself.
These attributes were added in numpygh-18536 but the fallback path was
not checked there.

Replaces numpygh-21813, although something more like it may make sense
if it allows us to just delete MachAr completely.
@charris charris merged commit 4db1023 into numpy:main Jun 26, 2022
@charris
Copy link
Member

charris commented Jun 26, 2022

Thanks Sebastian.

@seberg seberg deleted the fixup-error-valgrind branch June 27, 2022 12:27
@seberg seberg added the 09 - Backport-Candidate PRs tagged should be backported label Jun 27, 2022
@seberg
Copy link
Member Author

seberg commented Jun 27, 2022

I suspect we should backport this, to close gh-21827. I would not worry much about backporting for valgrind only, but msys2 running into issue (maybe due to a h5py change) warrents a backport probably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants