Step NumPy pin to 1.22 in conda build config#1024
Merged
xaleryb merged 1 commit intoIntelPython:masterfrom Dec 19, 2022
Merged
Conversation
Collaborator
Author
|
A verification job |
|
Array API standard conformance tests for dpctl=0.14.1dev0=py310h76be34b_24 ran successfully. |
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.
Intel 2023.0 release includes NumPy 1.22.
Thus
dpctlshould switch pinning NumPy version to the same value in config file.Otherwise it is impossible to correctly build
dpctl, when there is no new 2023 compiler in the host environment. This is because the current NumPy 1.21 can't be installed with the new 2023 compiler.As a result it leads to improper linkage of
libDPCTLSyclInterface.sowithlibsycl.so.6, which came with 2023 compiler only and present in build env, but missing in the host env.