Skip to content

Beta10 build #128

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 6 commits into from
Oct 8, 2020
Merged

Beta10 build #128

merged 6 commits into from
Oct 8, 2020

Conversation

Alexander-Makaryev
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Oct 8, 2020

Codecov Report

Merging #128 into master will decrease coverage by 51.45%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #128       +/-   ##
==========================================
- Coverage   51.45%   0.00%   -51.46%     
==========================================
  Files          19      19               
  Lines        1240    1240               
  Branches      329     329               
==========================================
- Hits          638       0      -638     
- Misses        340    1240      +900     
+ Partials      262       0      -262     
Impacted Files Coverage Δ
dpnp/config.py 0.00% <0.00%> (-100.00%) ⬇️
dpnp/_version.py 0.00% <0.00%> (-100.00%) ⬇️
dpnp/linalg/__init__.py 0.00% <0.00%> (-100.00%) ⬇️
dpnp/random/__init__.py 0.00% <0.00%> (-100.00%) ⬇️
dpnp/dpnp_iface_types.py 0.00% <0.00%> (-93.34%) ⬇️
dpnp/dpnp_iface.py 0.00% <0.00%> (-89.86%) ⬇️
dpnp/dpnp_iface_linearalgebra.py 0.00% <0.00%> (-84.79%) ⬇️
dpnp/linalg/linalg_iface.py 0.00% <0.00%> (-82.36%) ⬇️
dpnp/dpnp_iface_mathematical.py 0.00% <0.00%> (-61.73%) ⬇️
dpnp/dpnp_iface_searching.py 0.00% <0.00%> (-60.00%) ⬇️
... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2903875...2f5f9a0. Read the comment docs.

@shssf shssf merged commit cd310d1 into master Oct 8, 2020
@shssf shssf deleted the beta10-build branch October 8, 2020 22:09
antonwolfy added a commit that referenced this pull request Feb 18, 2025
There is currently no way to install dpnp with any numpy version > 2.0,
because
- there is no such version available on
`https://software.repos.intel.com/python/conda/` channel
- numpy from `conda-forge` channel depends on BLAS libraries which has a
runtime dependency `mkl < 2025.0` (since BLAS packages with build number
29)

There is draft PR
([gh-128](conda-forge/blas-feedstock#128)) to
build BLAS with MKL version 2025.0, but it is blocked due to MKL issue
([gh-83](conda-forge/intel_repack-feedstock#83)).

Meanwhile there was conda-forge patch
([gh-959](conda-forge/conda-forge-repodata-patches-feedstock#959))
merged recently to add `mkl < 2025.0` constraint to already published
BLAS packaged on `conda-forge` with older build number.

DPNP package can't fulfill the requirement `mkl < 2025.0`, because it
would mandate dpnp build pinning with DPC++ compiler 2024.2. While there
were non-backward compatible changes between 2024.2 and 2025.x versions,
that is dpnp built with 2024.2 compiler can not be installed with any
DPC++ RT 2025.x version, but it is required since targeted by the
upcoming release.

Thus the PR proposes to temporary disable or workaround all scenario
where it is need to tests with numpy from `conda-forge` channel,
including tests workflows for python 3.13 (per PR trigger and nightly)
and workflow for testing of oneMath interfaces with the latest numpy.
The changes has to be rolled back once the above issues are resolved.
github-actions bot added a commit that referenced this pull request Feb 18, 2025
There is currently no way to install dpnp with any numpy version > 2.0,
because
- there is no such version available on
`https://software.repos.intel.com/python/conda/` channel
- numpy from `conda-forge` channel depends on BLAS libraries which has a
runtime dependency `mkl < 2025.0` (since BLAS packages with build number
29)

There is draft PR
([gh-128](conda-forge/blas-feedstock#128)) to
build BLAS with MKL version 2025.0, but it is blocked due to MKL issue
([gh-83](conda-forge/intel_repack-feedstock#83)).

Meanwhile there was conda-forge patch
([gh-959](conda-forge/conda-forge-repodata-patches-feedstock#959))
merged recently to add `mkl < 2025.0` constraint to already published
BLAS packaged on `conda-forge` with older build number.

DPNP package can't fulfill the requirement `mkl < 2025.0`, because it
would mandate dpnp build pinning with DPC++ compiler 2024.2. While there
were non-backward compatible changes between 2024.2 and 2025.x versions,
that is dpnp built with 2024.2 compiler can not be installed with any
DPC++ RT 2025.x version, but it is required since targeted by the
upcoming release.

Thus the PR proposes to temporary disable or workaround all scenario
where it is need to tests with numpy from `conda-forge` channel,
including tests workflows for python 3.13 (per PR trigger and nightly)
and workflow for testing of oneMath interfaces with the latest numpy.
The changes has to be rolled back once the above issues are resolved. b09533e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants