Skip to content
Indy Plenum - Push Workflow

Merge pull request #1712 from tinkerer-shubh/test/fix-workflow-permis… #39

Sign in to view logs

Merge pull request #1712 from tinkerer-shubh/test/fix-workflow-permis…

Merge pull request #1712 from tinkerer-shubh/test/fix-workflow-permis… #39

Triggered via push February 18, 2025 18:45
@WadeBarnesWadeBarnes
pushed f7c5d5f
ubuntu-22.04
Status Success
Total duration 48m 52s
Artifacts 3

Push.yaml

on: push
Initialize Workflow
6s
Initialize Workflow
Lint  /  Lint
15s
Lint / Lint
Create Builder Image  /  Create Builder Image
1m 15s
Create Builder Image / Create Builder Image
Build Packages  /  Build 3rd Party Dependencies
15m 39s
Build Packages / Build 3rd Party Dependencies
Build Packages  /  Set Version
13s
Build Packages / Set Version
Build Packages  /  Build Release
1m 41s
Build Packages / Build Release
Build Packages  /  Build Python Packages
1m 22s
Build Packages / Build Python Packages
Matrix: Test Plenum / Module Tests
Matrix: Test Plenum / Sliced Module Tests
Publish Artifacts  /  Publish Artifacts
1m 5s
Publish Artifacts / Publish Artifacts
Fit to window
Zoom out
Zoom in

Annotations

17 warnings
Test Plenum / Module Tests (common)
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
Test Plenum / Module Tests (crypto)
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
Test Plenum / Module Tests (storage)
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
Test Plenum / Module Tests (state)
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
Test Plenum / Module Tests (ledger)
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
Test Plenum / Sliced Module Tests (plenum, 1)
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
Test Plenum / Module Tests (stp_zmq)
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
Test Plenum / Sliced Module Tests (plenum, 4)
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
Test Plenum / Sliced Module Tests (plenum, 8)
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
Test Plenum / Sliced Module Tests (plenum, 7)
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
Test Plenum / Sliced Module Tests (plenum, 3)
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
Test Plenum / Sliced Module Tests (plenum, 6)
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
Test Plenum / Sliced Module Tests (plenum, 2)
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
Test Plenum / Sliced Module Tests (plenum, 5)
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 Digest
plenum-deb Expired
968 KB
sha256:96d9991afe26935565c7eadb7a452c6a7fb9709e6dd91d047e8bafe34e864fb6
plenum-python Expired
2.22 MB
sha256:7e40fd2b2bf44c7e7c91e8d29527a129c94b282ae01dbdf8eb1dc4373495ba84
third-party-dependencies Expired
119 MB
sha256:6981dffd0eb73aa6ce9bae4358d58e02650fb150a6266b50d74fee43b486e9ef