Skip to content
Release

K Framework Release v7.1.177 #1537

Sign in to view logs

K Framework Release v7.1.177

K Framework Release v7.1.177 #1537

Triggered via release November 27, 2024 10:03
@rv-jenkinsrv-jenkins
prereleased v7.1.177
Status Success
Total duration 52m 22s
Artifacts 4

release.yml

on: release
Set Release ID
0s
Set Release ID
Create source tarball
51s
Create source tarball
K Ubuntu Jammy Package
27m 13s
K Ubuntu Jammy Package
Matrix: k-framework-binary cachix release
K Ubuntu Noble Package
30m 55s
K Ubuntu Noble Package
Build MacOS Package
38m 1s
Build MacOS Package
Build Pyk Documentation
4m 23s
Build Pyk Documentation
Test MacOS Package
2m 39s
Test MacOS Package
Publish Release
1m 6s
Publish Release
Publish pyk
35s
Publish pyk
GitHub Pages deployment
8m 23s
GitHub Pages deployment
Notify Dependents
6s
Notify Dependents
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 9 warnings
Build MacOS Package
The process '/opt/homebrew/bin/git' failed with exit code 1
Build MacOS Package
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Test MacOS Package
ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Test MacOS Package
The process '/opt/homebrew/bin/git' failed with exit code 1
Publish Release
Process completed with exit code 1.
k-framework-binary cachix release (ubuntu-24.04, ubuntu-24.04)
No push credentials found. Ignoring the 'useDaemon' option.
Build MacOS Package
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
Build MacOS Package
Unable to clean or reset the repository. The repository will be recreated instead.
Test MacOS Package
Unable to clean or reset the repository. The repository will be recreated instead.
Test MacOS Package
Cannot verify integrity of 'kframework--7.1.177.arm64_sonoma.bottle.1160.tar.gz'. No checksum was provided. For your reference, the checksum is: sha256 "61ac7895b91eeb7a17f5036ec4432c06e4660a5cd6c110a5c544025f3540d071"
Test MacOS Package
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
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
homebrew
356 MB
kframework_amd64_ubuntu_jammy.deb Expired
175 MB
kframework_amd64_ubuntu_noble.deb Expired
174 MB
pyk-docs Expired
8.39 MB