Skip to content
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

BUG: Ensure compile errors are raised correclty #21472

Merged
merged 1 commit into from May 9, 2022

Conversation

charris
Copy link
Member

@charris charris commented May 8, 2022

Backport of #21442.

This has been bugging me for a bit. The concurrent.futures Executor
requires checking the result for the error to be raised. That makes
sense, but just means we need to consume the result explicitly here
to ensure we know about compile errors.

Otherwise, compile errors just pass silently (which is very confusing
if the old object files are still around and the tests run based on
the old version).

This has been bugging me for a bit.  The concurrent.futures Executor
requires checking the result for the error to be raised.  That makes
sense, but just means we need to consume the result explicitly here
to ensure we know about compile errors.

Otherwise, compile errors just pass silently (which is very confusing
if the old object files are still around and the tests run based on
the old version).
@charris charris added 00 - Bug 08 - Backport Used to tag backport PRs labels May 8, 2022
@charris charris added this to the 1.22.4 release milestone May 8, 2022
@charris charris merged commit 159438b into numpy:maintenance/1.22.x May 9, 2022
@charris charris deleted the backport-21442 branch May 9, 2022 00:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00 - Bug 08 - Backport Used to tag backport PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants