Skip to content

Run all checks

Run all checks #1545

Triggered via schedule September 13, 2025 00:36
Status Failure
Total duration 53m 14s
Artifacts 6

ci.yml

on: schedule
Evaluate changes
8s
Evaluate changes
Matrix: Store requirements for LKG updates
Matrix: Run notebooks
Matrix: Run tests
Matrix: Build package / build_wheels
Build package  /  Build sdist
2m 42s
Build package / Build sdist
Build documentation  /  Create and publish documentation
11m 28s
Build documentation / Create and publish documentation
Lint code
16s
Lint code
Coverage report
20s
Coverage report
Build package  /  Merge artifacts
6s
Build package / Merge artifacts
Build documentation  /  Publish documentation
0s
Build documentation / Publish documentation
Matrix: Merge artifacts
Build package  /  Publish to PyPI or TestPyPI
0s
Build package / Publish to PyPI or TestPyPI
Matrix: Generate updated last known good files
Verify CI checks
2s
Verify CI checks
Merge last known good versions
4s
Merge last known good versions
Fit to window
Zoom out
Zoom in

Annotations

63 errors, 5 warnings, and 31 notices
Store requirements for LKG updates (tests, macos-latest, 3.12)
Process completed with exit code 1.
Store requirements for LKG updates (tests, ubuntu-latest, 3.12)
Process completed with exit code 1.
Store requirements for LKG updates (tests, ubuntu-latest, 3.11)
Process completed with exit code 1.
Store requirements for LKG updates (tests, ubuntu-latest, 3.13)
Process completed with exit code 1.
Store requirements for LKG updates (tests, macos-latest, 3.13)
Process completed with exit code 1.
Store requirements for LKG updates (tests, macos-latest, 3.11)
Process completed with exit code 1.
Store requirements for LKG updates (tests, windows-latest, 3.11)
Process completed with exit code 1.
Store requirements for LKG updates (tests, windows-latest, 3.13)
Process completed with exit code 1.
Store requirements for LKG updates (tests, windows-latest, 3.12)
Process completed with exit code 1.
Run notebooks (customer-scenarios)
Process completed with exit code 1.
Run tests (macos-latest, 3.13, dml)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, other)
Process completed with exit code 1.
Run notebooks (except-customer-scenarios)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, treatment)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, serial)
Process completed with exit code 1.
Run tests (windows-latest, 3.11, dml)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, dml)
Process completed with exit code 1.
Run tests (macos-latest, 3.11, treatment)
Process completed with exit code 1.
Run tests (macos-latest, 3.11, ray)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.13, main)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, other)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, ray)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, dml)
Process completed with exit code 1.
Run tests (macos-latest, 3.11, main)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, ray)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, serial)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, treatment)
Process completed with exit code 1.
Run tests (windows-latest, 3.11, serial)
Process completed with exit code 1.
Run tests (windows-latest, 3.11, other)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.12, main)
Process completed with exit code 1.
Run tests (macos-latest, 3.12, other)
Process completed with exit code 1.
Run tests (windows-latest, 3.11, treatment)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.13, dml)
Process completed with exit code 1.
Run tests (windows-latest, 3.13, dml)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.13, treatment)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.11, main)
Process completed with exit code 1.
Run tests (windows-latest, 3.11, main)
Process completed with exit code 1.
Run tests (windows-latest, 3.12, main)
Process completed with exit code 1.
Run tests (windows-latest, 3.12, treatment)
Process completed with exit code 1.
Run tests (macos-latest, 3.11, dml)
Process completed with exit code 1.
Run tests (windows-latest, 3.13, serial)
Process completed with exit code 1.
Run tests (windows-latest, 3.13, other)
Process completed with exit code 1.
Run tests (macos-latest, 3.12, treatment)
Process completed with exit code 1.
Run tests (windows-latest, 3.12, serial)
Process completed with exit code 1.
Run tests (windows-latest, 3.13, treatment)
Process completed with exit code 1.
Run tests (windows-latest, 3.12, other)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.13, serial)
Process completed with exit code 1.
Run tests (macos-latest, 3.12, main)
Process completed with exit code 1.
Run tests (macos-latest, 3.12, dml)
Process completed with exit code 1.
Run tests (macos-latest, 3.13, treatment)
Process completed with exit code 1.
Run tests (ubuntu-latest, 3.13, other)
Process completed with exit code 1.
Run tests (macos-latest, 3.12, ray)
Process completed with exit code 1.
Run tests (macos-latest, 3.13, main)
Process completed with exit code 1.
Run tests (macos-latest, 3.11, other)
Process completed with exit code 1.
Run tests (windows-latest, 3.13, main)
Process completed with exit code 1.
Run tests (windows-latest, 3.12, dml)
Process completed with exit code 1.
Run tests (macos-latest, 3.13, other)
Process completed with exit code 1.
Verify CI checks
Process completed with exit code 1.
Merge artifacts (lkg-notebooks)
No artifacts found matching pattern 'lkg-notebooks-*'
Merge artifacts (notebooks)
No artifacts found matching pattern 'notebooks-*'
Generate updated last known good files (notebooks)
Unable to download artifact(s): Artifact not found for name: lkg-notebooks Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Build package / Build wheels on macos-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
Build package / Build wheels on windows-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
Build package / Build wheels on ubuntu-latest
cibuildwheel 3 will require Python 3.11+, please upgrade the Python version used to run cibuildwheel. This does not affect the versions you can target when building wheels. See: https://cibuildwheel.pypa.io/en/stable/#what-does-it-do
Generate updated last known good files (tests)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
Generate updated last known good files (notebooks)
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
Store requirements for LKG updates (tests, windows-latest, 3.11)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Store requirements for LKG updates (tests, windows-latest, 3.13)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Store requirements for LKG updates (tests, windows-latest, 3.12)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Store requirements for LKG updates (tests, windows-latest, 3.10)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Store requirements for LKG updates (tests, windows-latest, 3.9)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.11, dml)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Build package / Build wheels on windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.9, treatment)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.11, serial)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.11, other)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.11, treatment)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.13, dml)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.11, main)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.12, main)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.12, treatment)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.13, serial)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.9, dml)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.13, other)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.10, other)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.12, serial)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.9, main)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.13, treatment)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.12, other)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.10, dml)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.9, other)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.10, serial)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.13, main)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.12, dml)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.10, treatment)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.10, main)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Run tests (windows-latest, 3.9, serial)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677

Artifacts

Produced during runtime
Name Size Digest
coverage
1.05 MB
sha256:c85f42ab67570546758a22b27ed82776f777d849e7f23bf6415f765cd225bec0
dist
48.9 MB
sha256:44143cb370ac934b92768c87d6589eb0a5ffe90b6dfb4624e7aee2f87c90b273
docs
6.07 MB
sha256:28f32a3e99e6fd43955b519cdbc825a9f78e041912254a2dcf0efd9fcfc901fc
lkg-files
5.41 KB
sha256:283d6ebb78c27e23ac9d133ea19531ca3699c9d301b1898d46d3a86c8935df3c
requirements
17 KB
sha256:3d45b40c186504e4cd50d62fe5d229c206890f9f892cf6ffc293b7f1ea5cedea
tests
34.9 KB
sha256:4e14f31ac8999171d659ad3a3a4f097381108e750c142276c4932cafa37c2b59