Skip to content

Skip "is out of bounds for array of dimension" #959

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

Conversation

LukichevaPolina
Copy link
Contributor

No description provided.

Copy link

@samir-nasibli samir-nasibli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fix is not provided.

@LukichevaPolina LukichevaPolina changed the title fix is out of bounds for array of dimension Skip "is out of bounds for array of dimension" Sep 22, 2021
@LukichevaPolina
Copy link
Contributor Author

The tests are skipped because function get_array_module in test_sort.py which compares usmarray and dpnp.ndarray works incorrectly and we cannot change cupy tests.

@Alexander-Makaryev
Copy link
Contributor

For details look into #979

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.

4 participants