Skip to content

build: move coffea 0.7.x to pyproject.toml #5513

build: move coffea 0.7.x to pyproject.toml

build: move coffea 0.7.x to pyproject.toml #5513

Triggered via pull request November 19, 2024 17:32
Status Cancelled
Total duration 9m 42s
Artifacts

ci.yml

on: pull_request
pre-commit
25s
pre-commit
Matrix: test
Matrix: test coffea-workqueue
Matrix: deploy release
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 1 warning
test coffea-workqueue (3.11)
Process completed with exit code 1.
test coffea (windows-latest) - python 3.9, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (windows-latest) - python 3.9, JDK17
The operation was canceled.
test coffea (windows-latest) - python 3.11, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (windows-latest) - python 3.11, JDK17
The operation was canceled.
test coffea (ubuntu-latest) - python 3.9, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (ubuntu-latest) - python 3.9, JDK17
The operation was canceled.
test coffea (ubuntu-latest) - python 3.11, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (ubuntu-latest) - python 3.11, JDK17
The operation was canceled.
test coffea (macOS-latest) - python 3.11, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (macOS-latest) - python 3.11, JDK17
The operation was canceled.
test coffea (macOS-latest) - python 3.9, JDK17
Canceling since a higher priority waiting request for 'CI/CD-refs/pull/1207/merge' exists
test coffea (macOS-latest) - python 3.9, JDK17
The operation was canceled.
test coffea-workqueue (3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, conda-incubator/setup-miniconda@v2.2.0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/