[INFO] cloning repository https://github.com/sortalongo/gas_sim [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/sortalongo/gas_sim" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fsortalongo%2Fgas_sim", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fsortalongo%2Fgas_sim'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] decc77477631efe552f03baa660036fbeb906e93 [INFO] testing sortalongo/gas_sim against try#c2e32f1c9652b13ed99608599c1e855462f421f3 for pr-146098-7 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fsortalongo%2Fgas_sim" "/workspace/builds/worker-6-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-6-tc2/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/sortalongo/gas_sim [INFO] finished tweaking git repo https://github.com/sortalongo/gas_sim [INFO] tweaked toml for git repo https://github.com/sortalongo/gas_sim written to /workspace/builds/worker-6-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/sortalongo/gas_sim on toolchain c2e32f1c9652b13ed99608599c1e855462f421f3 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/sortalongo/gas_sim already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 5672b513602b89cfb15ff2817211743926c3d4891a0a6f505efae4a8669de90c [INFO] running `Command { std: "docker" "start" "-a" "5672b513602b89cfb15ff2817211743926c3d4891a0a6f505efae4a8669de90c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "5672b513602b89cfb15ff2817211743926c3d4891a0a6f505efae4a8669de90c", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5672b513602b89cfb15ff2817211743926c3d4891a0a6f505efae4a8669de90c", kill_on_drop: false }` [INFO] [stdout] 5672b513602b89cfb15ff2817211743926c3d4891a0a6f505efae4a8669de90c [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 77612323a9df7321573e0f2949e7349bae0036df285759efb85b4939183ed780 [INFO] running `Command { std: "docker" "start" "-a" "77612323a9df7321573e0f2949e7349bae0036df285759efb85b4939183ed780", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Compiling winapi-build v0.1.1 [INFO] [stderr] Compiling libc v0.1.10 [INFO] [stderr] Compiling winapi v0.2.4 [INFO] [stderr] Compiling advapi32-sys v0.1.2 [INFO] [stderr] Compiling log v0.3.2 [INFO] [stderr] Compiling fern v0.3.5 [INFO] [stderr] Compiling rand v0.3.11 [INFO] [stderr] Compiling particles v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `FloatOps` [INFO] [stdout] --> src/space.rs:3:27 [INFO] [stdout] | [INFO] [stdout] 3 | use super::{custom_float, FloatOps, Particle, Time}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space.rs:51:16 [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter<'_, Particle>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_box.rs:47:16 [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_vec.rs:28:16 [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.03s [INFO] running `Command { std: "docker" "inspect" "77612323a9df7321573e0f2949e7349bae0036df285759efb85b4939183ed780", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "77612323a9df7321573e0f2949e7349bae0036df285759efb85b4939183ed780", kill_on_drop: false }` [INFO] [stdout] 77612323a9df7321573e0f2949e7349bae0036df285759efb85b4939183ed780 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 7784abe4c04f55d30859e5796141d41e9a735c5c02baf85f2da733df4bc185be [INFO] running `Command { std: "docker" "start" "-a" "7784abe4c04f55d30859e5796141d41e9a735c5c02baf85f2da733df4bc185be", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Compiling quickcheck v0.2.24 [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `FloatOps` [INFO] [stdout] --> src/space.rs:3:27 [INFO] [stdout] | [INFO] [stdout] 3 | use super::{custom_float, FloatOps, Particle, Time}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space.rs:51:16 [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter<'_, Particle>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_box.rs:47:16 [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_vec.rs:28:16 [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling particles v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:44:3 [INFO] [stdout] | [INFO] [stdout] 44 | info!("starting"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:45:3 [INFO] [stdout] | [INFO] [stdout] 45 | debug!("first state: {:?}", init); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:50:7 [INFO] [stdout] | [INFO] [stdout] 50 | debug!("t: {:?}", s.time); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:53:9 [INFO] [stdout] | [INFO] [stdout] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/main.rs:65:3 [INFO] [stdout] | [INFO] [stdout] 65 | info!("ending"); [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/bounds.rs:60:7 [INFO] [stdout] | [INFO] [stdout] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `FloatOps` [INFO] [stdout] --> src/space.rs:3:27 [INFO] [stdout] | [INFO] [stdout] 3 | use super::{custom_float, FloatOps, Particle, Time}; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space.rs:29:9 [INFO] [stdout] | [INFO] [stdout] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:68:5 [INFO] [stdout] | [INFO] [stdout] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/space_box.rs:70:7 [INFO] [stdout] | [INFO] [stdout] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused imports: `Bounds` and `SpaceVec` [INFO] [stdout] --> src/space_box.rs:97:58 [INFO] [stdout] | [INFO] [stdout] 97 | use super::super::{Collision, Particle, Space, Vector, SpaceVec, Bounds, Time}; [INFO] [stdout] | ^^^^^^^^ ^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around assigned value [INFO] [stdout] --> src/space_box.rs:121:13 [INFO] [stdout] | [INFO] [stdout] 121 | let l = ((TOP_RIGHT.0).1 - P1.r); [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 121 - let l = ((TOP_RIGHT.0).1 - P1.r); [INFO] [stdout] 121 + let l = (TOP_RIGHT.0).1 - P1.r ; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `Space` [INFO] [stdout] --> src/space_vec.rs:95:32 [INFO] [stdout] | [INFO] [stdout] 95 | use super::super::{Particle, Space, Vector}; [INFO] [stdout] | ^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space.rs:51:16 [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 51 | fn particles(&self) -> slice::Iter<'_, Particle>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_box.rs:47:16 [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 47 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/space_vec.rs:28:16 [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 28 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 1.13s [INFO] running `Command { std: "docker" "inspect" "7784abe4c04f55d30859e5796141d41e9a735c5c02baf85f2da733df4bc185be", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7784abe4c04f55d30859e5796141d41e9a735c5c02baf85f2da733df4bc185be", kill_on_drop: false }` [INFO] [stdout] 7784abe4c04f55d30859e5796141d41e9a735c5c02baf85f2da733df4bc185be [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/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" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+c2e32f1c9652b13ed99608599c1e855462f421f3" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 76754a9054183f602040ac4a9fa8c913d4e88d2f93758b9f32e562164e28e934 [INFO] running `Command { std: "docker" "start" "-a" "76754a9054183f602040ac4a9fa8c913d4e88d2f93758b9f32e562164e28e934", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/bounds.rs:60:7 [INFO] [stderr] | [INFO] [stderr] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/bounds.rs:60:7 [INFO] [stderr] | [INFO] [stderr] 60 | error!("Bounds encountered an illegal state: t: {}, p: {:?}", t, p); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unused import: `FloatOps` [INFO] [stderr] --> src/space.rs:3:27 [INFO] [stderr] | [INFO] [stderr] 3 | use super::{custom_float, FloatOps, Particle, Time}; [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/space.rs:29:9 [INFO] [stderr] | [INFO] [stderr] 29 | error!("Collision::t_unsafe called on Collision::Free"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `error` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/space_box.rs:68:5 [INFO] [stderr] | [INFO] [stderr] 68 | debug!("next_collision: {:?}", first_coll); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/space_box.rs:70:7 [INFO] [stderr] | [INFO] [stderr] 70 | debug!("bounce distance: {:?}", (&next1.x - &next2.x).norm()); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/space.rs:51:16 [INFO] [stderr] | [INFO] [stderr] 51 | fn particles(&self) -> slice::Iter; [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 51 | fn particles(&self) -> slice::Iter<'_, Particle>; [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/space_box.rs:47:16 [INFO] [stderr] | [INFO] [stderr] 47 | fn particles(&self) -> slice::Iter { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 47 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/space_vec.rs:28:16 [INFO] [stderr] | [INFO] [stderr] 28 | fn particles(&self) -> slice::Iter { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 28 | fn particles(&self) -> slice::Iter<'_, Particle> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: `particles` (lib) generated 24 warnings (15 duplicates) (run `cargo fix --lib -p particles` to apply 4 suggestions) [INFO] [stderr] warning: unused imports: `Bounds` and `SpaceVec` [INFO] [stderr] --> src/space_box.rs:97:58 [INFO] [stderr] | [INFO] [stderr] 97 | use super::super::{Collision, Particle, Space, Vector, SpaceVec, Bounds, Time}; [INFO] [stderr] | ^^^^^^^^ ^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unnecessary parentheses around assigned value [INFO] [stderr] --> src/space_box.rs:121:13 [INFO] [stderr] | [INFO] [stderr] 121 | let l = ((TOP_RIGHT.0).1 - P1.r); [INFO] [stderr] | ^ ^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_parens)]` (part of `#[warn(unused)]`) on by default [INFO] [stderr] help: remove these parentheses [INFO] [stderr] | [INFO] [stderr] 121 - let l = ((TOP_RIGHT.0).1 - P1.r); [INFO] [stderr] 121 + let l = (TOP_RIGHT.0).1 - P1.r ; [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: unused import: `Space` [INFO] [stderr] --> src/space_vec.rs:95:32 [INFO] [stderr] | [INFO] [stderr] 95 | use super::super::{Particle, Space, Vector}; [INFO] [stderr] | ^^^^^ [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:44:3 [INFO] [stderr] | [INFO] [stderr] 44 | info!("starting"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:44:3 [INFO] [stderr] | [INFO] [stderr] 44 | info!("starting"); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:45:3 [INFO] [stderr] | [INFO] [stderr] 45 | debug!("first state: {:?}", init); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:50:7 [INFO] [stderr] | [INFO] [stderr] 50 | debug!("t: {:?}", s.time); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `debug` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:53:9 [INFO] [stderr] | [INFO] [stderr] 53 | warn!("found overlapping particles:\n{:?}\n{:?}", p1, p2); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `log_level` [INFO] [stderr] --> src/main.rs:65:3 [INFO] [stderr] | [INFO] [stderr] 65 | info!("ending"); [INFO] [stderr] | ^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `log` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `log` may come from an old version of the `log` crate, try updating your dependency with `cargo update -p log` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `log` which comes from the expansion of the macro `info` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `particles` (lib test) generated 27 warnings (24 duplicates) (run `cargo fix --lib -p particles --tests` to apply 3 suggestions) [INFO] [stderr] warning: `particles` (bin "particles" test) generated 25 warnings (19 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.04s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/particles-0debe6a30604e100) [INFO] [stdout] [INFO] [stdout] running 10 tests [INFO] [stdout] test bounded_rand::tests::custom_float_can_be_constant ... ok [INFO] [stdout] test bounded_rand::tests::vector_is_bounded ... ok [INFO] [stdout] test particle::tests::quadratic_formula_simple ... ok [INFO] [stdout] test space_box::tests::particles_collide_before_wall ... ok [INFO] [stdout] test space_box::tests::single_particle_hits_wall ... ok [INFO] [stdout] test space_vec::tests::two_particles_yield_one_pair ... ok [INFO] [stdout] test particle::tests::impact_time_symmetrical_partices ... ok [INFO] [stdout] test particle::tests::bounce_symmetrical_particles ... ok [INFO] [stdout] test cartesian_iter::tests::length_is_2_choose_l ... ok [INFO] [stdout] test bounded_rand::tests::custom_float_is_bounded ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.06s [INFO] [stdout] [INFO] [stderr] Running unittests src/main.rs (/opt/rustwide/target/debug/deps/particles-c28abed66d4c6169) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Doc-tests particles [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "76754a9054183f602040ac4a9fa8c913d4e88d2f93758b9f32e562164e28e934", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "76754a9054183f602040ac4a9fa8c913d4e88d2f93758b9f32e562164e28e934", kill_on_drop: false }` [INFO] [stdout] 76754a9054183f602040ac4a9fa8c913d4e88d2f93758b9f32e562164e28e934