Skip to content
CI

validation: hacky way for no BLOCK_FAILED_CHILD #209

Sign in to view logs

validation: hacky way for no BLOCK_FAILED_CHILD

validation: hacky way for no BLOCK_FAILED_CHILD #209

Triggered via push March 10, 2025 05:34
@stratospherstratospher
pushed 4c0ef27
202412_fuzz_checkblockindex_pr
Status Failure
Total duration 2h 5m 10s
Artifacts –

ci.yml

on: push
test each commit
0s
test each commit
ASan + LSan + UBSan + integer, no depends, USDT
18m 31s
ASan + LSan + UBSan + integer, no depends, USDT
Matrix: macos-native-arm64
Matrix: win64-native
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
ASan + LSan + UBSan + integer, no depends, USDT
Process completed with exit code 2.
Win64 native, VS 2022
Process completed with exit code 1.
macOS 14 native, arm64, fuzz
The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 120 minutes.
macOS 14 native, arm64, no depends, sqlite only, gui
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
macOS 14 native, arm64, fuzz
Runner GitHub Actions 2 did not respond to a cancelation request with 00:05:00.
macOS 14 native, arm64, fuzz
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!