Dec 02 22:09:52.397 INFO testing postscript-0.13.2 against 1.30.1 for beta-1.31-5
Dec 02 22:09:52.397 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/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 +1.30.1 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 22:09:52.795 INFO [stdout] 532f5b33db64e8dad1d5e849a5438fc2f3917929c989434aa939450697518d61
Dec 02 22:09:52.803 INFO running `"docker" "start" "-a" "532f5b33db64e8dad1d5e849a5438fc2f3917929c989434aa939450697518d61"`
Dec 02 22:09:53.919 INFO [stderr] usermod: no changes
Dec 02 22:09:53.978 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 02 22:09:53.979 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 02 22:09:53.979 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 22:09:53.979 INFO [stderr] files will be included as a test target:
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] * /source/tests/compact1.rs
Dec 02 22:09:53.979 INFO [stderr] * /source/tests/type2.rs
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 22:09:53.979 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 02 22:09:53.979 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 02 22:09:53.979 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 22:09:53.979 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] For more information on this warning you can consult
Dec 02 22:09:53.979 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 22:09:53.979 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 22:09:53.979 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 22:09:53.979 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 22:09:53.979 INFO [stderr] files will be included as a benchmark target:
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] * /source/benches/compact1.rs
Dec 02 22:09:53.979 INFO [stderr] * /source/benches/type2.rs
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 22:09:53.979 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 22:09:53.979 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 22:09:53.979 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 22:09:53.979 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 22:09:53.979 INFO [stderr] 
Dec 02 22:09:53.979 INFO [stderr] For more information on this warning you can consult
Dec 02 22:09:53.979 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 22:09:53.983 INFO [stderr]    Compiling postscript v0.13.2 (/source)
Dec 02 22:09:56.215 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.27s
Dec 02 22:09:56.215 INFO [stderr] su: No module specific data is present
Dec 02 22:09:56.760 INFO running `"docker" "inspect" "532f5b33db64e8dad1d5e849a5438fc2f3917929c989434aa939450697518d61"`
Dec 02 22:09:57.009 INFO running `"docker" "rm" "-f" "532f5b33db64e8dad1d5e849a5438fc2f3917929c989434aa939450697518d61"`
Dec 02 22:09:57.250 INFO [stdout] 532f5b33db64e8dad1d5e849a5438fc2f3917929c989434aa939450697518d61
Dec 02 22:09:57.257 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-2/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-5/1.30.1:/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 +1.30.1 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 22:09:57.609 INFO [stdout] 94d9cc8dc6336d61e839fa2230824cca6e7f145a849a25d54e67277b6df70da8
Dec 02 22:09:57.619 INFO running `"docker" "start" "-a" "94d9cc8dc6336d61e839fa2230824cca6e7f145a849a25d54e67277b6df70da8"`
Dec 02 22:09:58.607 INFO [stderr] usermod: no changes
Dec 02 22:09:58.666 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 02 22:09:58.666 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 02 22:09:58.667 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 22:09:58.667 INFO [stderr] files will be included as a test target:
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] * /source/tests/compact1.rs
Dec 02 22:09:58.667 INFO [stderr] * /source/tests/type2.rs
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 22:09:58.667 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 02 22:09:58.667 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 02 22:09:58.667 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 22:09:58.667 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] For more information on this warning you can consult
Dec 02 22:09:58.667 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 22:09:58.667 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 22:09:58.667 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 22:09:58.667 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 22:09:58.667 INFO [stderr] files will be included as a benchmark target:
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] * /source/benches/compact1.rs
Dec 02 22:09:58.667 INFO [stderr] * /source/benches/type2.rs
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 22:09:58.667 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 22:09:58.667 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 22:09:58.667 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 22:09:58.667 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 22:09:58.667 INFO [stderr] 
Dec 02 22:09:58.667 INFO [stderr] For more information on this warning you can consult
Dec 02 22:09:58.667 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 22:09:58.676 INFO [stderr]    Compiling postscript v0.13.2 (/source)
Dec 02 22:10:02.297 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.66s
Dec 02 22:10:02.300 INFO [stderr] su: No module specific data is present
Dec 02 22:10:02.961 INFO running `"docker" "inspect" "94d9cc8dc6336d61e839fa2230824cca6e7f145a849a25d54e67277b6df70da8"`
Dec 02 22:10:03.341 INFO running `"docker" "rm" "-f" "94d9cc8dc6336d61e839fa2230824cca6e7f145a849a25d54e67277b6df70da8"`
Dec 02 22:10:03.687 INFO [stdout] 94d9cc8dc6336d61e839fa2230824cca6e7f145a849a25d54e67277b6df70da8
