Nov 07 05:09:37.272 INFO checking ETCDEVTeam/sputnikvm-dev against master#24e66c28980442a48d9458f1a4f9b76cc722dc8a for pr-55687 Nov 07 05:09:37.273 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55687/worker-1/master#24e66c28980442a48d9458f1a4f9b76cc722dc8a:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55687/master#24e66c28980442a48d9458f1a4f9b76cc722dc8a:/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 +24e66c28980442a48d9458f1a4f9b76cc722dc8a-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 07 05:09:37.742 INFO blam! e4e7f6cd6bcd29f4028f0e58145865b22f0e4abf0ae27ee98169e3c87dc30dc2 Nov 07 05:09:37.744 INFO running `"docker" "start" "-a" "e4e7f6cd6bcd29f4028f0e58145865b22f0e4abf0ae27ee98169e3c87dc30dc2"` Nov 07 05:09:39.732 INFO kablam! usermod: no changes Nov 07 05:09:39.792 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 07 05:09:39.792 INFO kablam! disables Cargo from automatically inferring other binary targets. Nov 07 05:09:39.792 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Nov 07 05:09:39.792 INFO kablam! files will be included as a binary target: Nov 07 05:09:39.792 INFO kablam! Nov 07 05:09:39.792 INFO kablam! * /source/src/main.rs Nov 07 05:09:39.792 INFO kablam! Nov 07 05:09:39.792 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Nov 07 05:09:39.792 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself Nov 07 05:09:39.792 INFO kablam! and disable this warning by adding `autobins = false` to your [package] Nov 07 05:09:39.792 INFO kablam! section. You may also move the files to a location where Cargo would not Nov 07 05:09:39.792 INFO kablam! automatically infer them to be a target, such as in subfolders. Nov 07 05:09:39.792 INFO kablam! Nov 07 05:09:39.792 INFO kablam! For more information on this warning you can consult Nov 07 05:09:39.792 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Nov 07 05:09:39.792 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `svmdev`, Nov 07 05:09:39.792 INFO kablam! please set bin.path in Cargo.toml Nov 07 05:09:40.119 INFO kablam! Checking elastic-array-plus v0.9.1 Nov 07 05:09:40.119 INFO kablam! Checking etcommon-hexutil v0.2.3 Nov 07 05:09:40.134 INFO kablam! Checking blockchain v0.2.0 Nov 07 05:09:40.134 INFO kablam! Compiling secp256k1-plus v0.5.7 Nov 07 05:09:40.135 INFO kablam! Checking arrayvec v0.3.25 Nov 07 05:09:40.135 INFO kablam! Checking num-integer v0.1.36 Nov 07 05:09:40.136 INFO kablam! Checking generic-array v0.8.3 Nov 07 05:09:40.136 INFO kablam! Checking bn-plus v0.4.4 Nov 07 05:09:43.312 INFO kablam! Checking parking_lot v0.4.8 Nov 07 05:09:43.881 INFO kablam! Checking globset v0.1.4 Nov 07 05:09:45.189 INFO kablam! Checking jsonrpc-core v7.1.1 Nov 07 05:09:45.944 INFO kablam! Checking num-bigint v0.1.43 Nov 07 05:09:46.688 INFO kablam! Checking digest v0.6.2 Nov 07 05:09:46.716 INFO kablam! Checking block-buffer v0.2.0 Nov 07 05:09:47.592 INFO kablam! Checking etcommon-rlp v0.2.3 Nov 07 05:09:50.940 INFO kablam! Checking sha3 v0.6.0 Nov 07 05:09:50.941 INFO kablam! Checking ripemd160 v0.6.0 Nov 07 05:09:50.941 INFO kablam! Checking sha2 v0.6.0 Nov 07 05:09:52.283 INFO kablam! Checking etcommon-bigint v0.2.9 Nov 07 05:09:54.165 INFO kablam! Checking jsonrpc-pubsub v7.1.1 Nov 07 05:09:54.165 INFO kablam! Checking jsonrpc-server-utils v7.1.1 Nov 07 05:09:58.833 INFO kablam! Checking etcommon-bloom v0.2.1 Nov 07 05:09:58.833 INFO kablam! Checking etcommon-block-core v0.1.0 Nov 07 05:09:58.833 INFO kablam! Checking etcommon-trie v0.3.11 Nov 07 05:10:01.593 INFO kablam! Checking jsonrpc-macros-plus v7.1.4 Nov 07 05:10:02.760 INFO kablam! Checking jsonrpc-http-server-plus v7.1.0 Nov 07 05:10:03.367 INFO kablam! Checking etcommon-block v0.3.4 Nov 07 05:10:07.553 INFO kablam! Checking sputnikvm v0.10.1 Nov 07 05:10:11.303 INFO kablam! Checking sputnikvm-precompiled-modexp v0.10.0 Nov 07 05:10:11.305 INFO kablam! Checking sputnikvm-precompiled-bn128 v0.10.0 Nov 07 05:10:11.307 INFO kablam! Checking sputnikvm-stateful v0.10.0 Nov 07 05:10:11.328 INFO kablam! Checking sputnikvm-network-ubiq v0.10.0 Nov 07 05:10:11.329 INFO kablam! Checking sputnikvm-network-classic v0.10.0 Nov 07 05:10:11.330 INFO kablam! Checking sputnikvm-network-musicoin v0.10.0 Nov 07 05:10:11.331 INFO kablam! Checking sputnikvm-network-ellaism v0.10.0 Nov 07 05:10:18.198 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.198 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:13 Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.198 INFO kablam! | ^^^^^ Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.198 INFO kablam! note: the associated type `>::Guard` must be valid for the block suffix following statement 0 at 471:9... Nov 07 05:10:18.198 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:9 Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! 471 | / let state = self.state(); Nov 07 05:10:18.198 INFO kablam! 472 | | let account = state.get(&address); Nov 07 05:10:18.198 INFO kablam! 473 | | Nov 07 05:10:18.198 INFO kablam! 474 | | match account { Nov 07 05:10:18.198 INFO kablam! ... | Nov 07 05:10:18.198 INFO kablam! 479 | | } Nov 07 05:10:18.198 INFO kablam! 480 | | } Nov 07 05:10:18.198 INFO kablam! | |_____^ Nov 07 05:10:18.198 INFO kablam! note: ...so that variable is valid at time of its declaration Nov 07 05:10:18.198 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:13 Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.198 INFO kablam! | ^^^^^ Nov 07 05:10:18.198 INFO kablam! Nov 07 05:10:18.198 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.198 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:13 Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.198 INFO kablam! | ^^^^^ Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.198 INFO kablam! note: the associated type `>::Guard` must be valid for the block at 470:125... Nov 07 05:10:18.198 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:470:125 Nov 07 05:10:18.198 INFO kablam! | Nov 07 05:10:18.198 INFO kablam! 470 | pub fn storage_state<'a>(&'a self, address: Address) -> Option>::Guard, H256, M256>> { Nov 07 05:10:18.198 INFO kablam! | _____________________________________________________________________________________________________________________________^ Nov 07 05:10:18.198 INFO kablam! 471 | | let state = self.state(); Nov 07 05:10:18.198 INFO kablam! 472 | | let account = state.get(&address); Nov 07 05:10:18.199 INFO kablam! 473 | | Nov 07 05:10:18.199 INFO kablam! ... | Nov 07 05:10:18.199 INFO kablam! 479 | | } Nov 07 05:10:18.199 INFO kablam! 480 | | } Nov 07 05:10:18.199 INFO kablam! | |_____^ Nov 07 05:10:18.199 INFO kablam! note: ...so that references are valid when the destructor runs Nov 07 05:10:18.199 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:13 Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.199 INFO kablam! | ^^^^^ Nov 07 05:10:18.199 INFO kablam! Nov 07 05:10:18.199 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.199 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:21 Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.199 INFO kablam! | ^^^^^^^^^^^^ Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.199 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 471:21... Nov 07 05:10:18.199 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:21 Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.199 INFO kablam! | ^^^^^^^^^^^^ Nov 07 05:10:18.199 INFO kablam! note: ...so type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` of expression is valid during the expression Nov 07 05:10:18.199 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:21 Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.199 INFO kablam! | ^^^^^^^^^^^^ Nov 07 05:10:18.199 INFO kablam! Nov 07 05:10:18.199 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.199 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:21 Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.199 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.199 INFO kablam! | ^^^^^^^^^^^^ Nov 07 05:10:18.199 INFO kablam! | Nov 07 05:10:18.207 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.207 INFO kablam! note: the associated type `>::Guard` must be valid for the destruction scope surrounding statement at 471:9... Nov 07 05:10:18.207 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:9 Nov 07 05:10:18.207 INFO kablam! | Nov 07 05:10:18.207 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.207 INFO kablam! | ^^^^^^^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.207 INFO kablam! note: ...so that references are valid when the destructor runs Nov 07 05:10:18.207 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:471:21 Nov 07 05:10:18.207 INFO kablam! | Nov 07 05:10:18.207 INFO kablam! 471 | let state = self.state(); Nov 07 05:10:18.208 INFO kablam! | ^^^^^^^^^^^^ Nov 07 05:10:18.208 INFO kablam! Nov 07 05:10:18.208 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.208 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 472:23... Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.208 INFO kablam! note: ...so that method receiver is valid for the method call Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! Nov 07 05:10:18.208 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.208 INFO kablam! note: the associated type `>::Guard` must be valid for the expression at 472:23... Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! note: ...so type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` of expression is valid during the expression Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! Nov 07 05:10:18.208 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.208 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 472:23... Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.208 INFO kablam! note: ...so that the type `trie::FixedSecureTrie<>::Guard, bigint::H160, block::Account>` is not borrowed for too long Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! Nov 07 05:10:18.208 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.208 INFO kablam! note: the associated type `>::Guard` must be valid for the expression at 472:23... Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! note: ...so that auto-reference is valid at the time of borrow Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^ Nov 07 05:10:18.208 INFO kablam! Nov 07 05:10:18.208 INFO kablam! error[E0311]: the associated type `>::Guard` may not live long enough Nov 07 05:10:18.208 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.208 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.208 INFO kablam! | Nov 07 05:10:18.208 INFO kablam! = help: consider adding an explicit lifetime bound for `>::Guard` Nov 07 05:10:18.208 INFO kablam! note: the associated type `>::Guard` must be valid for the method call at 472:23... Nov 07 05:10:18.209 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.209 INFO kablam! | Nov 07 05:10:18.209 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.209 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.209 INFO kablam! note: ...so that a type/lifetime parameter is in scope here Nov 07 05:10:18.209 INFO kablam! --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/sputnikvm-stateful-0.10.0/src/lib.rs:472:23 Nov 07 05:10:18.209 INFO kablam! | Nov 07 05:10:18.209 INFO kablam! 472 | let account = state.get(&address); Nov 07 05:10:18.209 INFO kablam! | ^^^^^^^^^^^^^^^^^^^ Nov 07 05:10:18.209 INFO kablam! Nov 07 05:10:18.229 INFO kablam! error: aborting due to 9 previous errors Nov 07 05:10:18.229 INFO kablam! Nov 07 05:10:18.229 INFO kablam! For more information about this error, try `rustc --explain E0311`. Nov 07 05:10:18.249 INFO kablam! error: Could not compile `sputnikvm-stateful`. Nov 07 05:10:18.249 INFO kablam! warning: build failed, waiting for other jobs to finish... Nov 07 05:10:19.156 INFO kablam! error: build failed Nov 07 05:10:19.156 INFO kablam! su: No module specific data is present Nov 07 05:10:19.964 INFO running `"docker" "rm" "-f" "e4e7f6cd6bcd29f4028f0e58145865b22f0e4abf0ae27ee98169e3c87dc30dc2"` Nov 07 05:10:20.228 INFO blam! e4e7f6cd6bcd29f4028f0e58145865b22f0e4abf0ae27ee98169e3c87dc30dc2