Skip to content

Build and test conda packages and wheels - #3151

Open
jharlow-intel wants to merge 1 commit into
masterfrom
ci/intel-python-ci
Open

jharlow-intel wants to merge 1 commit into
masterfrom
ci/intel-python-ci

Conversation

@jharlow-intel

@jharlow-intel jharlow-intel commented Nov 3, 2026 •

Copy link
Copy Markdown
Collaborator

Adds ci/ and .github/workflows/intel-ci.yml, which build the conda packages and wheels for Linux and Windows on every declared Python, and test each in a clean environment.

  • conda-recipe/ is now the only recipe: the conda-forge one that was conda-recipe-cf/. It builds against conda-forge, with dpctl's dev builds from dppy/label/dev after it. The Intel-channel recipe, with rattler_recipe.yaml, conda-package.yml, conda-package-cf.yml and conda-build-test.yml are removed; the Array API conformance and pybind11 examples jobs move to intel-ci.yml.
  • The dppy/label/dev uploads and their cleanup move into intel-ci.yml, for pushes to master and tags only.
  • Wheels build with cibuildwheel and icx 2026.2 against the dpctl wheel on PyPI, and require the oneAPI runtime wheels (dpcpp-cpp-rt, intel-sycl-rt, mkl, onemkl-sycl-*), as the PyPI wheels do, each at least the version the build used ([tool.gh-ci.pin-compatible]). Their tests take dpctl's dev wheels from the dppy/label/dev index. PyPI has no dpctl for 3.15 yet, so the 3.15 classifier is dropped until it does.
  • ci/test.py runs dpnp.tests, then dpnp.tests.tensor, against the installed package, and fails when it finds no SYCL device: the OpenCL CPU device in Actions, or a GPU with GH_CI_DEVICE=gpu.

The required checks on master come from conda-package.yml, so they need replacing with this workflow's, such as Test Linux Python 3.11, before this can merge.

Validation: run 43919353056 built and tested the conda packages and the wheels for 3.11, the newest regular Python and 3.14t on Linux and Windows, and ran the examples and the Array API job. Not run yet: a GPU, and the uploads, which only master and tags do.

@jharlow-intel jharlow-intel self-assigned this Nov 3, 2026
@jharlow-intel jharlow-intel changed the title Build and test conda packages and wheels for Intel Python CI Build and test conda packages and wheels Nov 5, 2026
@jharlow-intel
jharlow-intel force-pushed the ci/intel-python-ci branch 2 times, most recently from 6aca46e to e9f220a Compare November 9, 2026 14:42
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

View rendered docs @ https://intelpython.github.io/dpnp/pull/3151/index.html

@github-actions

github-actions Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Array API standard conformance tests for dpnp=0.22.0dev2+7.g283e2552c ran successfully.
Passed: 1491
Failed: 0
Skipped: 6

@coveralls

coveralls commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Coverage Status

coverage: 84.269%. remained the same — ci/intel-python-ci into master

Comment thread .github/workflows/intel-ci.yml Resolved
Comment thread ci/test.py Resolved
Comment thread conda-recipe/meta.yaml Resolved
Comment thread .github/workflows/conda-package-cf.yml Resolved
Comment thread ci/hooks.py Resolved
Comment thread doc/quick_start_guide.rst Resolved
Comment thread AGENTS.md Outdated
| --- | --- | --- |
| pre-commit (`Check`) | `.github/workflows/pre-commit.yml` | yes |
| conda build and tests, Linux and Windows, py3.13-3.15 and 3.14t (`Test (...)`) | `conda-package.yml` | yes |
| conda packages and wheels built and tested, Linux and Windows, py3.11-3.15 and 3.14t for conda, py3.10-3.14 and 3.14t for wheels (`Test <Platform> Python <version>`, `Test <Platform> Wheels Python <version>`); the conda matrix is `conda-recipe/conda_build_config.yaml`, the wheel matrix the Python classifiers in `pyproject.toml`; see `ci/README.md` | `intel-ci.yml` | no |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The wheels are 3.11-3.14 and 3.14t: pyproject.toml has no 3.10 classifier, as #3173 dropped 3.10. Also, the old row was required on master. Is a required check planned for intel-ci.yml, or should branch protection just drop the old Test (...) checks?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Fixed the wheel range to 3.11-3.14 and 3.14t. The required Test (...) checks come from conda-package.yml, which this PR removes, so branch protection needs them swapped for intel-ci.yml's jobs before this can merge.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

add1e50 has the right wheel range, thanks. If intel-ci.yml's test jobs replace the required Test (...) checks, this row should say yes in the last column, as the old one did.

Comment thread ci/matrix.py Resolved
Comment thread ci/config.yml Resolved
Comment thread CHANGELOG.md Resolved
@jharlow-intel
jharlow-intel force-pushed the ci/intel-python-ci branch 2 times, most recently from b53329b to c93fd5e Compare November 10, 2026 22:49
Comment thread .github/workflows/conda-package.yml Resolved
Comment thread pyproject.toml Resolved
@antonwolfy antonwolfy added this to the 0.22.0 release milestone Nov 16, 2026
Adds a ci/ directory and .github/workflows/intel-ci.yml, which build the
conda packages and the wheels for every declared platform and Python and
test each with ci/test.py. A pull request builds the oldest and the newest
regular Python and the newest free-threaded one, and every push and tag run
gets a concurrency group of its own.

conda-recipe/ is now the only recipe, the conda-forge one that was
conda-recipe-cf/. The Intel-channel recipe and conda-package.yml are
removed, and so are conda-package-cf.yml and its conda-build-test.yml,
whose builds intel-ci.yml repeats.
The dev uploads to anaconda.org and their cleanup, the Array API conformance
job and the pybind11 examples move to intel-ci.yml. The examples and the Array API job
wait only for the builds of the newest regular and free-threaded Linux
packages, which every event builds, and install dpnp from the built
packages only.

The benchmarks take PyYAML from conda-forge, as PyPI has no Python 3.15
wheel for it yet. ci/build.py refuses two built packages with the same file
name, which would overwrite each other in its flat output directory, and
takes METADATA's line ending from its headers. conda-build records the
commit each conda package came from in info/about.json, and LDFLAGS links
the Linux wheels' libraries with full RELRO.

ci/test.py reruns a failed suite, twice for the main tests and three times
for the tensor tests, and stops a tensor test stuck for 120 s. GH_CI_DEVICE
and ONEAPI_DEVICE_SELECTOR reach the tests. The recipe ignores mkl-dpcpp's
run export, and the ci/ scripts carry the BSD-3 header.

The conda builds and test environments take dpctl's dev builds from
dppy/label/dev after conda-forge, with flexible channel priority, and the
wheel tests from its pip index after PyPI: ci/build.py and ci/hooks.py get
--channel and --extra-index-url from intel-ci.yml. The examples and the
Array API job pin dpnp to the exact build. [tool.gh-ci.pin-compatible] maps
each runtime wheel to the compiler or oneMKL package the build installed;
the Linux before-all and ci/install_icx.py print those versions and
ci/build.py requires >= each, < its next major. The upload takes each
wheel's version from its file name and fails when there is nothing to
upload. Every job sets conda up with .github/actions/setup-miniconda.
Comment thread .github/AGENTS.md
- Every job sets `timeout-minutes`; for a job that calls a reusable workflow, set it inside the called workflow.
- `actionlint` runs in pre-commit.
- Set up conda with the local `.github/actions/setup-miniconda` action, which retries a failed setup once, instead of calling `conda-incubator/setup-miniconda` directly; a job that checks dpnp out into a subdirectory uses it from there (`./source/.github/actions/setup-miniconda`).
- `workflows/intel-ci.yml` is Intel CI: its conda matrix is `conda-recipe/conda_build_config.yaml`, its wheel matrix the Python classifiers in `pyproject.toml`, and its upload and cleanup jobs run only for pushes to `master` and tags in `IntelPython/dpnp`; see `ci/README.md`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

After the rebase, line 16 here and the comment at .github/dependabot.yml:21 (both from #3171) still name conda-recipe/rattler_recipe.yaml and conda-recipe-cf/meta.yaml, which this PR removes. With one recipe left, conda-recipe/meta.yaml is a dev-series pin and [build-system].requires the only release-only one. Could both places say that?

This branch has not been deployed

No deployments
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