Skip to content
Build Hero on Macos & Run tests

s #123

Sign in to view logs

s

s #123

Triggered via push February 5, 2025 07:23
@despiegkdespiegk
pushed 6eec7db
development_kristof10
Status Failure
Total duration 1m 50s
Artifacts –

hero_build_macos.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 10 notices
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L39
get_u8() returns `!u8`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L45
get_string() returns `!string`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L48
get_u16() returns `!u16`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L51
get_u8() returns `!u8`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L55
get_u16() returns `!u16`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L58
get_string() returns `!string`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L59
get_u32() returns `!u32`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L67
unwrapped Result cannot be used in an infix expression
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L39
get_u8() returns `!u8`, so it should have either an `or {}` block, or `!` at the end
build (aarch64-apple-darwin, macos-latest, macos-arm64): lib/data/radixtree/serialize.v#L45
get_string() returns `!string`, so it should have either an `or {}` block, or `!` at the end
build (x86_64-apple-darwin, macos-13, macos-i64)
The job was canceled because "aarch64-apple-darwin_maco" failed.
build (x86_64-apple-darwin, macos-13, macos-i64)
The operation was canceled.
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations
build (aarch64-apple-darwin, macos-latest, macos-arm64)
ambiguous expression. use `()` to ensure correct order of operations