[INFO] crate tessel 0.3.1 is already in cache [INFO] testing tessel-0.3.1 against 1.44.0 for beta-1.45-1 [INFO] extracting crate tessel 0.3.1 into /workspace/builds/worker-5/source [INFO] validating manifest of crates.io crate tessel 0.3.1 on toolchain 1.44.0 [INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate tessel 0.3.1 [INFO] finished tweaking crates.io crate tessel 0.3.1 [INFO] tweaked toml for crates.io crate tessel 0.3.1 written to /workspace/builds/worker-5/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+1.44.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /workspace/builds/worker-5/source/src/main.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] warning: path `/workspace/builds/worker-5/source/src/main.rs` was erroneously implicitly accepted for binary `hello-rust`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+1.44.0" "build" "--frozen"` [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] 0ede5094c982941eeec4a0189afcc0c4c3f6de8e7640062b1ef28d27f1ac2afc [INFO] running `"docker" "start" "-a" "0ede5094c982941eeec4a0189afcc0c4c3f6de8e7640062b1ef28d27f1ac2afc"` [INFO] [stderr] sudo: setrlimit(RLIMIT_CORE): Operation not permitted [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/src/main.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] warning: path `/opt/rustwide/workdir/src/main.rs` was erroneously implicitly accepted for binary `hello-rust`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] Compiling bit-vec v0.4.4 [INFO] [stderr] Compiling atomic-option v0.1.2 [INFO] [stderr] Compiling bit-set v0.4.0 [INFO] [stderr] Compiling tessel v0.3.1 (/opt/rustwide/workdir) [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/protocol.rs:122:17 [INFO] [stderr] | [INFO] [stderr] 122 | try!(socket.write_all(&[raw_cmd::ECHO, data.len() as u8])); [INFO] [stderr] | ^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(deprecated)]` on by default [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/protocol.rs:127:21 [INFO] [stderr] | [INFO] [stderr] 127 | try!(socket.write_all(&[raw_cmd::TX, slice.len() as u8])); [INFO] [stderr] | ^^^ [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/protocol.rs:128:21 [INFO] [stderr] | [INFO] [stderr] 128 | try!(socket.write_all(slice)); [INFO] [stderr] | ^^^ [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/protocol.rs:134:17 [INFO] [stderr] | [INFO] [stderr] 134 | try!(socket.write_all(&[raw_cmd::TXRX, data.len() as u8])); [INFO] [stderr] | ^^^ [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/lib.rs:292:9 [INFO] [stderr] | [INFO] [stderr] 292 | try!(sock.read_exact(&mut read_byte)); [INFO] [stderr] | ^^^ [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'try': use the `?` operator instead [INFO] [stderr] --> src/lib.rs:307:9 [INFO] [stderr] | [INFO] [stderr] 307 | try!(sock.read_exact(&mut read_byte)); [INFO] [stderr] | ^^^ [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'std::sync::ONCE_INIT': the `new` function is now preferred [INFO] [stderr] --> src/lib.rs:50:1 [INFO] [stderr] | [INFO] [stderr] 50 | / lazy_static! { [INFO] [stderr] 51 | | // Create a tuple with two ports, one on each domain socket path. [INFO] [stderr] 52 | | static ref TESSEL_PORTS: AtomicOption<(Port, Port)> = AtomicOption::new(Box::new(( [INFO] [stderr] 53 | | Port::new(PORT_A_UDS_PATH), [INFO] [stderr] 54 | | Port::new(PORT_B_UDS_PATH), [INFO] [stderr] 55 | | ))); [INFO] [stderr] 56 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: use of deprecated item 'std::sync::ONCE_INIT': the `new` function is now preferred [INFO] [stderr] --> src/lib.rs:50:1 [INFO] [stderr] | [INFO] [stderr] 50 | / lazy_static! { [INFO] [stderr] 51 | | // Create a tuple with two ports, one on each domain socket path. [INFO] [stderr] 52 | | static ref TESSEL_PORTS: AtomicOption<(Port, Port)> = AtomicOption::new(Box::new(( [INFO] [stderr] 53 | | Port::new(PORT_A_UDS_PATH), [INFO] [stderr] 54 | | Port::new(PORT_B_UDS_PATH), [INFO] [stderr] 55 | | ))); [INFO] [stderr] 56 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: 8 warnings emitted [INFO] [stderr] [INFO] [stderr] error[E0463]: can't find crate for `alloc_system` [INFO] [stderr] --> src/main.rs:2:1 [INFO] [stderr] | [INFO] [stderr] 2 | extern crate alloc_system; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate [INFO] [stderr] [INFO] [stderr] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0463`. [INFO] [stderr] error: could not compile `tessel`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "0ede5094c982941eeec4a0189afcc0c4c3f6de8e7640062b1ef28d27f1ac2afc"` [INFO] running `"docker" "rm" "-f" "0ede5094c982941eeec4a0189afcc0c4c3f6de8e7640062b1ef28d27f1ac2afc"` [INFO] [stdout] 0ede5094c982941eeec4a0189afcc0c4c3f6de8e7640062b1ef28d27f1ac2afc