We continuously test that our builds and tests pass on the latest GitHub Runners for:
- Debian Bookworm.
- If Zebra's build runs out of RAM, try setting
- If Zebra's tests timeout or run out of RAM, try running
cargo test -- --test-threads=2. Note that
cargouses all processor cores on your machine by default.
Some of Zebra's tests download Zcash blocks, so they might be unreliable
depending on your network connection. You can set
to skip the network tests.
Some of Zebra's tests deliberately cause errors that make Zebra panic. macOS records these panics as crash reports. If you are seeing "Crash Reporter" dialogs during Zebra tests, you can disable them using this Terminal.app command:
defaults write com.apple.CrashReporter DialogType none
Zebra usually syncs in around three days on Mainnet and half a day on
Testnet. The sync speed depends on your network connection and the overall Zcash
network load. The major constraint we've found on
zebrad performance is the
network weather, especially the ability to make good connections to other Zcash
network peers. If you're having trouble syncing, try the following config
Make sure you're using a release build on your native architecture.
If your connection is slow, try downloading fewer blocks at a time:
lookahead_limit = 1000
max_concurrent_block_requests = 25
If your connection is slow, try connecting to fewer peers:
peerset_initial_target_size = 25
Zebra logs at info level by default.
If Zebra is slow, make sure it is logging at info level:
filter = 'info'
Or restrict debug logging to a specific Zebra component:
filter = 'info,zebra_network=debug'
If you keep on seeing multiple info logs per second, please open a bug.