Nov 02 06:13:12.994 INFO checking sorpaas/etclient against try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7 for pr-55517 Nov 02 06:13:12.995 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55517/worker-2/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55517/try#dc8b02d6f1e93f212fc39844ea688b634b4a03c7:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +dc8b02d6f1e93f212fc39844ea688b634b4a03c7-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 02 06:13:13.400 INFO blam! 6a10d546965ea1e17267a1014296542d5fec152df57f6e365177dde6f2615a97 Nov 02 06:13:13.414 INFO running `"docker" "start" "-a" "6a10d546965ea1e17267a1014296542d5fec152df57f6e365177dde6f2615a97"` Nov 02 06:13:14.656 INFO kablam! usermod: no changes Nov 02 06:13:14.932 INFO kablam! Checking elastic-array-plus v0.9.0 Nov 02 06:13:14.950 INFO kablam! Checking etcommon-hexutil v0.2.2 Nov 02 06:13:14.950 INFO kablam! Checking blockchain v0.2.0 Nov 02 06:13:14.951 INFO kablam! Compiling secp256k1-plus v0.5.7 Nov 02 06:13:14.951 INFO kablam! Checking iovec v0.1.0 Nov 02 06:13:14.956 INFO kablam! Checking net2 v0.2.31 Nov 02 06:13:14.968 INFO kablam! Checking tokio-timer-plus v0.1.3 Nov 02 06:13:14.976 INFO kablam! Checking generic-array v0.8.3 Nov 02 06:13:16.744 INFO kablam! Checking bytes v0.4.5 Nov 02 06:13:17.216 INFO kablam! Checking digest v0.6.2 Nov 02 06:13:17.216 INFO kablam! Checking block-buffer v0.2.0 Nov 02 06:13:17.700 INFO kablam! Checking mio v0.6.10 Nov 02 06:13:18.920 INFO kablam! Checking sha3 v0.6.0 Nov 02 06:13:18.920 INFO kablam! Checking ripemd160 v0.6.0 Nov 02 06:13:18.920 INFO kablam! Checking sha2 v0.6.0 Nov 02 06:13:19.248 INFO kablam! Checking etcommon-rlp v0.2.2 Nov 02 06:13:20.780 INFO kablam! Checking tokio-io v0.1.3 Nov 02 06:13:22.481 INFO kablam! Checking etcommon-bigint v0.2.7 Nov 02 06:13:23.953 INFO kablam! Checking tokio-core v0.1.9 Nov 02 06:13:25.557 INFO kablam! Checking etcommon-bloom v0.2.1 Nov 02 06:13:25.557 INFO kablam! Checking etcommon-trie v0.3.8 Nov 02 06:13:25.557 INFO kablam! Checking ethash v0.3.0 Nov 02 06:13:26.149 INFO kablam! Checking rlpx v0.3.0 Nov 02 06:13:26.149 INFO kablam! Checking dpt v0.2.6 Nov 02 06:13:27.572 INFO kablam! Checking etcommon-block v0.3.2 Nov 02 06:13:28.743 INFO kablam! Checking sputnikvm v0.7.6 Nov 02 06:13:28.743 INFO kablam! Checking devp2p v0.3.1 Nov 02 06:13:30.964 INFO kablam! Checking sputnikvm-stateful v0.7.5 Nov 02 06:13:31.677 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:13 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.677 INFO kablam! | ^^^^^ Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.677 INFO kablam! note: the associated type `>::Guard` must be valid for the block suffix following statement 0 at 438:9... Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:9 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 438 | / let state = self.state(); Nov 02 06:13:31.677 INFO kablam! 439 | | let account = state.get(&address); Nov 02 06:13:31.677 INFO kablam! 440 | | Nov 02 06:13:31.677 INFO kablam! 441 | | match account { Nov 02 06:13:31.677 INFO kablam! ... | Nov 02 06:13:31.677 INFO kablam! 446 | | } Nov 02 06:13:31.677 INFO kablam! 447 | | } Nov 02 06:13:31.677 INFO kablam! | |_____^ Nov 02 06:13:31.677 INFO kablam! note: ...so that variable is valid at time of its declaration Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:13 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.677 INFO kablam! | ^^^^^ Nov 02 06:13:31.677 INFO kablam! Nov 02 06:13:31.677 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:13 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.677 INFO kablam! | ^^^^^ Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.677 INFO kablam! note: the associated type `>::Guard` must be valid for the block at 437:125... Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:437:125 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 437 | pub fn storage_state<'a>(&'a self, address: Address) -> Option>::Guard, H256, M256>> { Nov 02 06:13:31.677 INFO kablam! | _____________________________________________________________________________________________________________________________^ Nov 02 06:13:31.677 INFO kablam! 438 | | let state = self.state(); Nov 02 06:13:31.677 INFO kablam! 439 | | let account = state.get(&address); Nov 02 06:13:31.677 INFO kablam! 440 | | Nov 02 06:13:31.677 INFO kablam! ... | Nov 02 06:13:31.677 INFO kablam! 446 | | } Nov 02 06:13:31.677 INFO kablam! 447 | | } Nov 02 06:13:31.677 INFO kablam! | |_____^ Nov 02 06:13:31.677 INFO kablam! note: ...so that references are valid when the destructor runs Nov 02 06:13:31.677 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:13 Nov 02 06:13:31.677 INFO kablam! | Nov 02 06:13:31.677 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.677 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! Nov 02 06:13:31.678 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:21 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.678 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 438:21... Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:21 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! note: ...so type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` of expression is valid during the expression Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:21 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! Nov 02 06:13:31.678 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:21 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.678 INFO kablam! note: the associated type `>::Guard` must be valid for the destruction scope surrounding statement at 438:9... Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:9 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! note: ...so that references are valid when the destructor runs Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:438:21 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 438 | let state = self.state(); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! Nov 02 06:13:31.678 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.678 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 439:23... Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.678 INFO kablam! note: ...so that method receiver is valid for the method call Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! Nov 02 06:13:31.678 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.678 INFO kablam! note: the associated type `>::Guard` must be valid for the expression at 439:23... Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! note: ...so type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` of expression is valid during the expression Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! Nov 02 06:13:31.678 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^ Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.678 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 439:23... Nov 02 06:13:31.678 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.678 INFO kablam! | Nov 02 06:13:31.678 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.678 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.679 INFO kablam! note: ...so that the type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` is not borrowed for too long Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^ Nov 02 06:13:31.679 INFO kablam! Nov 02 06:13:31.679 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^ Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.679 INFO kablam! note: the associated type `>::Guard` must be valid for the expression at 439:23... Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^ Nov 02 06:13:31.679 INFO kablam! note: ...so that auto-reference is valid at the time of borrow Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^ Nov 02 06:13:31.679 INFO kablam! Nov 02 06:13:31.679 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 02 06:13:31.679 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 439:23... Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.679 INFO kablam! note: ...so that a type/lifetime parameter is in scope here Nov 02 06:13:31.679 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.7.5/src/lib.rs:439:23 Nov 02 06:13:31.679 INFO kablam! | Nov 02 06:13:31.679 INFO kablam! 439 | let account = state.get(&address); Nov 02 06:13:31.679 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 02 06:13:31.679 INFO kablam! Nov 02 06:13:31.679 INFO kablam! error: aborting due to 9 previous errors Nov 02 06:13:31.679 INFO kablam! Nov 02 06:13:31.679 INFO kablam! For more information about this error, try `rustc --explain E0311`. Nov 02 06:13:31.692 INFO kablam! error: Could not compile `sputnikvm-stateful`. Nov 02 06:13:31.692 INFO kablam! Nov 02 06:13:31.692 INFO kablam! To learn more, run the command again with --verbose. Nov 02 06:13:31.700 INFO kablam! su: No module specific data is present Nov 02 06:13:32.898 INFO running `"docker" "rm" "-f" "6a10d546965ea1e17267a1014296542d5fec152df57f6e365177dde6f2615a97"` Nov 02 06:13:33.196 INFO blam! 6a10d546965ea1e17267a1014296542d5fec152df57f6e365177dde6f2615a97