K Framework Release v7.1.117 #1461
Triggered via release
August 22, 2024 06:39
rv-jenkins
prereleased
v7.1.117
Status
Success
Total duration
47m 37s
Artifacts
3
release.yml
on: release
Set Release ID
0s
Create source tarball
37s
K Ubuntu Jammy Package
18m 14s
Matrix: k-framework-binary cachix release
GitHub Pages deployment
7m 57s
Notify Dependents
8s
Annotations
5 errors and 8 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 (MacM1, self-macos-12)
The following actions use a deprecated Node.js version and will be forced to run on node20: workflow/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
k-framework-binary cachix release (ubuntu-24.04, ubuntu-24.04)
The following actions use a deprecated Node.js version and will be forced to run on node20: workflow/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
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
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
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
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
homebrew
Expired
|
356 MB |
|
kframework_amd64_ubuntu_jammy.deb
Expired
|
175 MB |
|
pyk-docs
Expired
|
3.69 MB |
|