Skip to content
Release

K Framework Release v7.1.180 #1540

Sign in to view logs

K Framework Release v7.1.180

K Framework Release v7.1.180 #1540

Triggered via release November 28, 2024 09:03
@rv-jenkinsrv-jenkins
prereleased v7.1.180
Status Success
Total duration 41m 54s
Artifacts 4

release.yml

on: release
Set Release ID
0s
Set Release ID
Create source tarball
36s
Create source tarball
K Ubuntu Jammy Package
25m 27s
K Ubuntu Jammy Package
Matrix: k-framework-binary cachix release
K Ubuntu Noble Package
16m 7s
K Ubuntu Noble Package
Build MacOS Package
26m 32s
Build MacOS Package
Build Pyk Documentation
4m 10s
Build Pyk Documentation
Test MacOS Package
3m 41s
Test MacOS Package
Publish Release
1m 1s
Publish Release
Publish pyk
38s
Publish pyk
GitHub Pages deployment
8m 41s
GitHub Pages deployment
Notify Dependents
7s
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.180.arm64_sonoma.bottle.1163.tar.gz'. No checksum was provided. For your reference, the checksum is: sha256 "a1ee33dddc524b62a6ebdb9510676a6120258b1ba593c3d10c87d01e5a5c50f1"
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
357 MB
kframework_amd64_ubuntu_jammy.deb Expired
175 MB
kframework_amd64_ubuntu_noble.deb Expired
174 MB
pyk-docs Expired
8.4 MB