Skip to content

feat: have "motive is not type correct" come with an explanation (#6168) #24730

feat: have "motive is not type correct" come with an explanation (#6168)

feat: have "motive is not type correct" come with an explanation (#6168) #24730

Triggered via push November 23, 2024 00:24
Status Cancelled
Total duration 14m 25s
Artifacts

ci.yml

on: push
configure
6s
configure
Matrix: build
Build matrix complete
0s
Build matrix complete
release
0s
release
release-nightly
0s
release-nightly
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 6 warnings
macOS aarch64
Canceling since a higher priority waiting request for 'CI-refs/heads/master-push' exists
macOS aarch64
The operation was canceled.
Linux release
Canceling since a higher priority waiting request for 'CI-refs/heads/master-push' exists
Linux release
The operation was canceled.
Linux
Canceling since a higher priority waiting request for 'CI-refs/heads/master-push' exists
Linux
The operation was canceled.
macOS aarch64
zstd 1.5.6 is already installed and up-to-date. To reinstall 1.5.6, run: brew reinstall zstd
macOS aarch64
gmp 6.3.0 is already installed and up-to-date. To reinstall 6.3.0, run: brew reinstall gmp
macOS aarch64
libuv 1.49.2 is already installed and up-to-date. To reinstall 1.49.2, run: brew reinstall libuv
macOS aarch64
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.
Linux release
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.
Linux
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.