Skip to content

Merge pull request #83 from lsst/u/timj/fix-pypi #711

Merge pull request #83 from lsst/u/timj/fix-pypi

Merge pull request #83 from lsst/u/timj/fix-pypi #711

Triggered via push February 20, 2025 09:55
Status Success
Total duration 20m 31s
Artifacts 9

build.yaml

on: push
Matrix: build_and_test
check-changes
5s
check-changes
Matrix: pypi_wheel_build
pypi_sdist_build
19s
pypi_sdist_build
pipy_upload
41s
pipy_upload
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
pypi_wheel_build (ubuntu-latest, 310)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
pypi_wheel_build (ubuntu-latest, 313)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
pypi_wheel_build (ubuntu-latest, 313)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
pypi_wheel_build (ubuntu-latest, 312)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
pypi_wheel_build (ubuntu-latest, 312)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
pypi_wheel_build (ubuntu-latest, 311)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
pypi_wheel_build (ubuntu-latest, 311)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
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
sphgeom-macos-latest-310
1.06 MB
sphgeom-macos-latest-311
1.07 MB
sphgeom-macos-latest-312
1.09 MB
sphgeom-macos-latest-313
1.09 MB
sphgeom-sdist
157 KB
sphgeom-ubuntu-latest-310
1.38 MB
sphgeom-ubuntu-latest-311
1.38 MB
sphgeom-ubuntu-latest-312
1.37 MB
sphgeom-ubuntu-latest-313
1.37 MB