Skip to content

CONTRACTS: is_fresh now tracks separation at the byte level instead of whole objects #1661

CONTRACTS: is_fresh now tracks separation at the byte level instead of whole objects

CONTRACTS: is_fresh now tracks separation at the byte level instead of whole objects #1661

Triggered via pull request February 27, 2025 22:41
Status Success
Total duration 7m 34s
Artifacts

bsd.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
FreeBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
FreeBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
NetBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
NetBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
OpenBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.
OpenBSD
Input 'save-always' has been deprecated with message: save-always does not work as intended and will be removed in a future release. A separate `actions/cache/restore` step should be used instead. See https://github.com/actions/cache/tree/main/save#always-save-cache for more details.