Build and test conda-recipe-cf for Intel Python CI by jharlow-intel · Pull Request #204 · IntelPython/mkl_random

jharlow-intel · 2026-10-23T20:23:40Z

Description

Adds what Intel Python CI (gh-ci) needs from mkl_random: a ci/ directory and a new workflow, .github/workflows/intel-ci.yml. The workflow builds conda-recipe-cf for every platform and Python version the recipe declares, and tests each package in a clean conda-forge environment with ci/test.py. Intel's Jenkins then waits for that run, tests each package again on its own machines, scans it, and for a release tag publishes the packages it tested. Jenkins isn't switched on for mkl_random yet, so until it is, this only adds a GitHub Actions workflow.

ci/matrix.py, ci/build.py, ci/hooks.py: the shared gh-ci scripts, standard library only. Here they look for conda-recipe-cf/ first and build Linux and Windows on GitHub-hosted runners. hooks.py installs the test requirements from ci/config.yml, the way Jenkins does.
ci/test.py: runs pytest --pyargs mkl_random against the installed package and writes a JUnit report.
ci/config.yml: the workflow, the artifact names (mkl_random {platform} Python {python}, as conda-package-cf.yml names them) and the test requirements, pytest.
conda-recipe-cf/conda_build_config.yaml: now lists the Python versions, the ones conda-package-cf.yml builds today, for ci/matrix.py, and numpy: '2'. Without a NumPy variant, conda-build falls back to NumPy 1.26, which has no builds for Python 3.13 and newer. conda-package-cf.yml passes --python and --numpy itself, so it is unaffected.
ci/README.md and AGENTS.md notes.

A pull request builds the two newest regular Python versions on Linux and Windows; pushes to master and tags build them all.

Miniforge is pinned to 26.7.2-0. Miniforge 26.9.4-0, released on 22 October, makes setup-miniconda's conda init fail on Windows runners, and the existing conda-package*.yml workflows, which install latest, hit it too on this pull request.

Overlap with #202. It also sets numpy: '2' in conda_build_config.yaml and drops Python 3.10, so whichever lands second needs a small rebase, and if 3.10 goes it should leave the python: list here too. conda-package-cf.yml and intel-ci.yml now both build conda-recipe-cf; retiring one can be a follow-up.

Verification

Tests: this pull request's Intel Python CI run built Linux and Windows for Python 3.14 and 3.15 and ran ci/test.py against each package: 380 passed on Linux 3.14 and on Windows 3.15.
Lint: pre-commit run on every changed file, all hooks passing, and zizmor on intel-ci.yml, no findings.
python ci/matrix.py lists 14 builds, Linux and Windows for 3.10 to 3.15 and 3.14t; with --event pull_request it lists 3.14 and 3.15 on both.
ci/config.yml loads with gh-ci's own parser.

Not verified

The builds a tag or a push to the default branch adds, Python 3.10 to 3.13 and 3.14t; they use the same jobs.
The Jenkins side, which isn't enabled for mkl_random yet.

Adds what Intel Python CI (gh-ci) needs from this repository: ci/ with the shared matrix, build and test-hook scripts, ci/test.py and ci/config.yml, and .github/workflows/intel-ci.yml, which builds conda-recipe-cf for every platform and Python version the recipe declares and tests each package in a clean conda-forge environment, as Jenkins later does. conda-recipe-cf/conda_build_config.yaml now declares the Python versions conda-package-cf.yml builds, for ci/matrix.py, and NumPy 2: without a numpy variant conda-build falls back to NumPy 1.26, which has no builds for Python 3.13 and newer. conda-package-cf.yml passes --python and --numpy itself, so it is unaffected.

…ws runners

antonwolfy · 2026-10-26T21:29:32Z

+
+concurrency:
+  group: intel-ci-${{ github.ref }}
+  cancel-in-progress: true


With cancel-in-progress: true keyed on github.ref, two quick merges cancel the first commit's whole run. Jenkins, which waits for that run, gets no packages for it.

Suggested change

cancel-in-progress: true

cancel-in-progress: ${{ github.event_name == 'pull_request' }}

antonwolfy · 2026-10-26T21:37:08Z

+numpy:
+    - '2'


That only will work when ##202 is merged

antonwolfy · 2026-10-26T21:45:27Z

@@ -1,3 +1,16 @@
+# The Python versions to build, one per line and without selectors: ci/matrix.py
+# reads them for .github/workflows/intel-ci.yml. NumPy 2, as in conda-forge's
+# global pinning; conda-package-cf.yml passes its own with --python and --numpy.


--numpy is dropping in #202

antonwolfy · 2026-10-26T21:47:12Z

+        "--artifacts", required=True, type=Path, help="the downloaded artifact"
+    )
+    parser.add_argument(
+        "--work", required=True, type=Path, help="an empty scratch directory"


hooks.py doesn't check that --work is empty, and may install conda-index into the user's base environment.

antonwolfy · 2026-10-26T21:48:47Z

+
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.12"


Is there any issue to use the newer python?

antonwolfy · 2026-10-26T21:53:59Z

+          activate-environment: ""
+          conda-remove-defaults: "true"
+
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0


Alternatively we can drop setup-python and run with shell: bash -el {0} with base activated.

bash is available on Windows runners too, and setup-miniconda supports this shell there. The step bodies become plain python ci/build.py … and python ci/hooks.py …. The $CONDA path code and hooks.py's re-run of itself would then only matter for local use.

antonwolfy · 2026-10-26T22:00:21Z

@@ -0,0 +1,135 @@
+# Intel Python CI (gh-ci) for mkl_random: builds the conda-forge recipe, conda-recipe-cf, for every


The same PR is open in three repos at once.
Have you considered moving common things (scripts, workflow) to some common repo like https://github.com/IntelPython/devops-tools ?
That would help to reduce the duplication.

A pull request now builds and tests the oldest and the newest regular Python versions the recipe declares, instead of the two newest, so the oldest supported Python is tested before a change merges rather than first on a release tag. Intel's Jenkins tests the same two.

jharlow-intel added 2 commits October 23, 2026 14:22

Pin Miniforge in Intel Python CI: 26.9.4-0 breaks conda init on Windo…

5d87148

…ws runners

jharlow-intel marked this pull request as ready for review October 23, 2026 20:42

jharlow-intel requested review from antonwolfy, ndgrigorian, vlad-perevezentsev and xaleryb as code owners October 23, 2026 20:42

antonwolfy added this to the 1.7.0 release milestone Oct 26, 2026

antonwolfy reviewed Oct 26, 2026

View reviewed changes

Navigation Menu

Repository navigation

Build and test conda-recipe-cf for Intel Python CI - #204

Build and test conda-recipe-cf for Intel Python CI#204
jharlow-intel wants to merge 3 commits into
masterfrom
ci/intel-python-ci

jharlow-intel commented Oct 23, 2026 •

edited

Loading

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

antonwolfy Oct 26, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	cancel-in-progress: true
	cancel-in-progress: ${{ github.event_name == 'pull_request' }}

		@@ -0,0 +1,135 @@
		# Intel Python CI (gh-ci) for mkl_random: builds the conda-forge recipe, conda-recipe-cf, for every

		numpy:
		- '2'

Conversation

jharlow-intel commented Oct 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Verification

Not verified

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

antonwolfy Oct 26, 2026

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jharlow-intel commented Oct 23, 2026 •

edited

Loading