Skip to content

feat(pkgrepo): impl new logic after migration to packages.broadcom.com #100

feat(pkgrepo): impl new logic after migration to packages.broadcom.com

feat(pkgrepo): impl new logic after migration to packages.broadcom.com #100

Triggered via pull request November 15, 2024 04:06
Status Failure
Total duration 1d 4h 38m 35s
Artifacts

kitchen.macos.yml

on: pull_request
Matrix: test-1015
Matrix: test-11
Matrix: test-12
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
test-12 (default-macos-12-latest-py3)
Process completed with exit code 20.
test-1015 (default-macos-1015-latest-py3)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
test-11 (default-macos-11-latest-py3)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
test-12 (default-macos-12-latest-py3)
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/
test-12 (default-macos-12-latest-py3)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test-12 (default-macos-12-latest-py3)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Kitchen (macOS)
The macOS-10.15 environment is deprecated, consider switching to macos-11(macos-latest), macos-12 instead. For more details see https://github.com/actions/virtual-environments/issues/5583