K Framework Release v7.1.213 #1573
Triggered via release
February 20, 2025 23:43
rv-jenkins
prereleased
v7.1.213
Status
Success
Total duration
1h 8m 23s
Artifacts
4
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
release.yml
on: release
Set Release ID
0s
Create source tarball
34s
K Ubuntu Jammy Package
52m 14s
Matrix: k-framework-binary cachix release
K Ubuntu Noble Package
58m 9s
GitHub Pages deployment
7m 40s
Notify Dependents
7s
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.213.arm64_sonoma.bottle.1196.tar.gz'.
No checksum was provided.
For your reference, the checksum is:
sha256 "3e5cedf0140b39d35b7b871df38c67fa506ffbef868c9e849c29f1396e1c60e3"
|
|
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 | Digest | |
|---|---|---|---|
|
homebrew
Expired
|
357 MB |
sha256:637215e14593a42b37f055504e5ee2602654cc3298bab5fc6399fe42d05c616b
|
|
|
kframework_amd64_ubuntu_jammy.deb
Expired
|
175 MB |
sha256:b50afab2a8a67295332ee2d9c0ac7c7121b2ba59201652970101f4fe24a6e6a3
|
|
|
kframework_amd64_ubuntu_noble.deb
Expired
|
174 MB |
sha256:01fe6a6cee189f9f102a9892dffe41004790d4d40781719d3599b3d0b06b6d8f
|
|
|
pyk-docs
Expired
|
8.47 MB |
sha256:8b6340130152b29c6a94ace1f2b75a2fe58fd22554719d4d8555ed38282219ed
|
|