IntelPython / dpnp / 13400320372

81%

push

github

Disable GitHub workflows to be run with python 3.13 (#2322)

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](https://github.com/conda-forge/blas-feedstock/pull/128)) to
build BLAS with MKL version 2025.0, but it is blocked due to MKL issue
([gh-83](https://github.com/conda-forge/intel_repack-feedstock/issues/83)).

Meanwhile there was conda-forge patch
([gh-959](https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/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.

4684 of 9472 branches covered (49.45%)

Branch coverage included in aggregate %.

17389 of 21295 relevant lines covered (81.66%)

20061.6 hits per line