Skip to content

zcash_primitives: Move the memo module to the zcash_protocol crate. #2566

zcash_primitives: Move the memo module to the zcash_protocol crate.

zcash_primitives: Move the memo module to the zcash_protocol crate. #2566

Triggered via push March 5, 2024 16:46
Status Failure
Total duration 8m 56s
Artifacts

ci.yml

on: push
Matrix: build-latest
Matrix: build-nodefault
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 5 warnings
Clippy (beta)
The process '/home/runner/.cargo/bin/cargo' failed with exit code 1
Latest build on ubuntu-latest
Process completed with exit code 101.
Latest build on windows-latest
The job was canceled because "ubuntu-latest" failed.
Latest build on windows-latest
The operation was canceled.
Latest build on macOS-latest
The job was canceled because "ubuntu-latest" failed.
Latest build on macOS-latest
The operation was canceled.
Build target wasm32-wasi
Process completed with exit code 101.
Bitrot check
Process completed with exit code 101.
protobuf consistency
Process completed with exit code 101.
binary operation `==` cannot be applied to type `std::result::Result<(zcash_client_backend::address::UnifiedAddress, zcash_primitives::zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>`: zcash_client_sqlite/src/lib.rs#L270
error[E0369]: binary operation `==` cannot be applied to type `std::result::Result<(zcash_client_backend::address::UnifiedAddress, zcash_primitives::zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>` --> zcash_client_sqlite/src/lib.rs:270:25 | 267 | Ok(usk | ________________________- 268 | | .to_unified_full_viewing_key() 269 | | .default_address(ua_request) | |____________________________________________________- std::result::Result<(zcash_client_backend::address::UnifiedAddress, zcash_primitives::zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError> 270 | == ufvk.default_address(ua_request)) | ^^ -------------------------------- std::result::Result<(zcash_client_backend::address::UnifiedAddress, zcash_primitives::zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>
binary operation `==` cannot be applied to type `std::result::Result<(zcash_client_backend::address::UnifiedAddress, zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>`: zcash_client_sqlite/src/lib.rs#L270
error[E0369]: binary operation `==` cannot be applied to type `std::result::Result<(zcash_client_backend::address::UnifiedAddress, zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>` --> zcash_client_sqlite/src/lib.rs:270:25 | 267 | Ok(usk | ________________________- 268 | | .to_unified_full_viewing_key() 269 | | .default_address(ua_request) | |____________________________________________________- std::result::Result<(zcash_client_backend::address::UnifiedAddress, zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError> 270 | == ufvk.default_address(ua_request)) | ^^ -------------------------------- std::result::Result<(zcash_client_backend::address::UnifiedAddress, zip32::DiversifierIndex), zcash_client_backend::keys::AddressGenerationError>
Clippy (MSRV)
Clippy had exited with the 101 exit code
Test on ubuntu-latest with --features zfuture
Process completed with exit code 101.
Test on ubuntu-latest with --features unstable-nu6
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on ubuntu-latest with --features unstable-nu6
Process completed with exit code 101.
Test on windows-latest with --features unstable-nu6
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on windows-latest with --features unstable-nu6
The operation was canceled.
Test on windows-latest with --features orchard
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on windows-latest with --features orchard
The operation was canceled.
Test on windows-latest
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on windows-latest
The operation was canceled.
Test on windows-latest with --features zfuture
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on windows-latest with --features zfuture
The operation was canceled.
Test on ubuntu-latest with --features orchard
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on ubuntu-latest with --features orchard
The operation was canceled.
Test on ubuntu-latest
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on ubuntu-latest
The operation was canceled.
Test on macOS-latest with --features orchard
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on macOS-latest with --features orchard
The operation was canceled.
Test on macOS-latest
The job was canceled because "ubuntu-latest_zfuture" failed.
Test on macOS-latest
The operation was canceled.
Code coverage
Process completed with exit code 1.
Clippy (beta)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Clippy (beta)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
protobuf consistency
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: supplypike/setup-bin@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Clippy (MSRV)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Clippy (MSRV)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/