Skip to content

LGPU add controlled adjoint support (#970) #10039

LGPU add controlled adjoint support (#970)

LGPU add controlled adjoint support (#970) #10039

Triggered via push November 8, 2024 22:45
Status Success
Total duration 8m 46s
Billable time 28m
Artifacts 6
Set wheel build matrix  /  set-builder-matrix
3s
Set wheel build matrix / set-builder-matrix
Matrix: build_dependencies
Matrix: linux-wheels-x86-64
Matrix: upload-pypi
Fit to window
Zoom out
Zoom in

Annotations

24 warnings
Linux::x86_64 - lightning_qubit (Python 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux::x86_64 - lightning_qubit (Python 3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux::x86_64 - lightning_qubit (Python 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux::x86_64 - lightning_kokkos (Python 3.12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux::x86_64 - lightning_kokkos (Python 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Linux::x86_64 - lightning_kokkos (Python 3.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-ecosystem/action-regex-match@main. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):
attestations input ignored
The workflow was run with the 'attestations: true' input, but an explicit password was also set, disabling Trusted Publishing. As a result, the attestations input is ignored.
Upgrade to Trusted Publishing
Trusted Publishers allows publishing packages to PyPI from automated environments like GitHub Actions without needing to use username/password combinations or API tokens to authenticate with PyPI. Read more: https://docs.pypi.org/trusted-publishers
Create a Trusted Publisher
A new Trusted Publisher for the currently running publishing workflow can be created by accessing the following link(s) while logged-in as an owner of the package(s):

Artifacts

Produced during runtime
Name Size
Linux-wheels-lightning_kokkos-py310-x86_64.zip Expired
3.98 MB
Linux-wheels-lightning_kokkos-py311-x86_64.zip Expired
3.98 MB
Linux-wheels-lightning_kokkos-py312-x86_64.zip Expired
3.98 MB
Linux-wheels-lightning_qubit-py310-x86_64.zip Expired
1.5 MB
Linux-wheels-lightning_qubit-py311-x86_64.zip Expired
1.5 MB
Linux-wheels-lightning_qubit-py312-x86_64.zip Expired
1.5 MB