[INFO] cloning repository https://github.com/dlight/pj [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/dlight/pj" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj'... [INFO] [stderr] error: copy-fd: write returned: No space left on device [INFO] [stderr] fatal: cannot copy '/usr/share/git-core/templates/hooks/post-update.sample' to '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj/hooks/post-update.sample': No space left on device [WARN] Retrying crate fetch in 3 seconds (attempt 1) [INFO] cloning repository https://github.com/dlight/pj [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/dlight/pj" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 3dadaef6cfbaa75da7ebe714163dc9196f5333fb [INFO] checking dlight/pj against try#c659ee110de67e82444e4b6c8407c1a9af9c2cf6 for pr-145608 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fdlight%2Fpj" "/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/dlight/pj [INFO] finished tweaking git repo https://github.com/dlight/pj [INFO] tweaked toml for git repo https://github.com/dlight/pj written to /workspace/builds/worker-6-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/dlight/pj on toolchain c659ee110de67e82444e4b6c8407c1a9af9c2cf6 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+c659ee110de67e82444e4b6c8407c1a9af9c2cf6" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/dlight/pj 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" "+c659ee110de67e82444e4b6c8407c1a9af9c2cf6" "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] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded memchr v0.1.3 [INFO] [stderr] Downloaded env_logger v0.3.1 [INFO] [stderr] Downloaded aho-corasick v0.2.2 [INFO] [stderr] Downloaded regex-syntax v0.1.2 [INFO] [stderr] Downloaded regex v0.1.39 [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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+c659ee110de67e82444e4b6c8407c1a9af9c2cf6" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 53a2162feb19a38657c71e51cd8752973ce6bc915969d805bdaf8c163c8d8c04 [INFO] running `Command { std: "docker" "start" "-a" "53a2162feb19a38657c71e51cd8752973ce6bc915969d805bdaf8c163c8d8c04", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "53a2162feb19a38657c71e51cd8752973ce6bc915969d805bdaf8c163c8d8c04", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "53a2162feb19a38657c71e51cd8752973ce6bc915969d805bdaf8c163c8d8c04", kill_on_drop: false }` [INFO] [stdout] 53a2162feb19a38657c71e51cd8752973ce6bc915969d805bdaf8c163c8d8c04 [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:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+c659ee110de67e82444e4b6c8407c1a9af9c2cf6" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 6a45eb88a1d0fe6b31c9a58165fe706b7214e6da15bd23224b075cf853199518 [INFO] running `Command { std: "docker" "start" "-a" "6a45eb88a1d0fe6b31c9a58165fe706b7214e6da15bd23224b075cf853199518", kill_on_drop: false }` [INFO] [stderr] warning: no edition set: defaulting to the 2015 edition while the latest is 2024 [INFO] [stderr] Checking libc v0.1.8 [INFO] [stderr] Checking regex-syntax v0.1.2 [INFO] [stderr] Checking memchr v0.1.3 [INFO] [stderr] Checking log v0.3.1 [INFO] [stderr] Checking aho-corasick v0.2.2 [INFO] [stderr] Checking regex v0.1.39 [INFO] [stderr] Checking env_logger v0.3.1 [INFO] [stderr] Checking pj v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/mod.rs:148:9 [INFO] [stdout] | [INFO] [stdout] 148 | try!(c.link(functions_vec)); [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(deprecated)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_link.rs:9:13 [INFO] [stdout] | [INFO] [stdout] 9 | try!(self.link_step(code)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_link.rs:33:41 [INFO] [stdout] | [INFO] [stdout] 33 | let (function, _) = try!(self.functions [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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 `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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/mod.rs:148:9 [INFO] [stdout] | [INFO] [stdout] 148 | try!(c.link(functions_vec)); [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(deprecated)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_link.rs:9:13 [INFO] [stdout] | [INFO] [stdout] 9 | try!(self.link_step(code)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_link.rs:33:41 [INFO] [stdout] | [INFO] [stdout] 33 | let (function, _) = try!(self.functions [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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 `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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:13:13 [INFO] [stdout] | [INFO] [stdout] 13 | debug!("There is no code"); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:19:9 [INFO] [stdout] | [INFO] [stdout] 19 | debug!("Program: {:?}", self.program); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:20:9 [INFO] [stdout] | [INFO] [stdout] 20 | debug!("Starting at {:?}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:24:17 [INFO] [stdout] | [INFO] [stdout] 24 | debug!("Implicit return at end of {}", self.fun_name()); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:27:17 [INFO] [stdout] | [INFO] [stdout] 27 | / debug!("{}\tPC {:?} {:?}\tStack: {:?}", [INFO] [stdout] 28 | | self.fun_name(), [INFO] [stdout] 29 | | self.counter, [INFO] [stdout] 30 | | self.program[self.counter], [INFO] [stdout] 31 | | self.data_stack); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:42:9 [INFO] [stdout] | [INFO] [stdout] 42 | debug!("-"); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:72:25 [INFO] [stdout] | [INFO] [stdout] 72 | let (f, p, _) = try!(self.functions [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:86:26 [INFO] [stdout] | [INFO] [stdout] 86 | let (fun, pos) = try!(self.get_fun(function_pos)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:94:21 [INFO] [stdout] | [INFO] [stdout] 94 | let frame = try!(self.call_stack.pop().ok_or(Halted)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:96:26 [INFO] [stdout] | [INFO] [stdout] 96 | let (fun, pos) = try!(self.get_fun(frame.function_start)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:123:19 [INFO] [stdout] | [INFO] [stdout] 123 | let top = try!(self.top()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:129:17 [INFO] [stdout] | [INFO] [stdout] 129 | let a = try!(self.pop()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:130:17 [INFO] [stdout] | [INFO] [stdout] 130 | let b = try!(self.pop()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:145:17 [INFO] [stdout] | [INFO] [stdout] 145 | let a = try!(self.top()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:148:34 [INFO] [stdout] | [INFO] [stdout] 148 | Equal => if a == 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:149:37 [INFO] [stdout] | [INFO] [stdout] 149 | NotEqual => if a != 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:150:39 [INFO] [stdout] | [INFO] [stdout] 150 | GreaterThan => if a > 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:151:36 [INFO] [stdout] | [INFO] [stdout] 151 | LessThan => if a < 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:152:41 [INFO] [stdout] | [INFO] [stdout] 152 | GreaterEqual => if a >= 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:153:38 [INFO] [stdout] | [INFO] [stdout] 153 | LessEqual => if a <= 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `log_level` [INFO] [stdout] --> src/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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/vm/vm_run.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | / debug!("{}\tPC {:?} Stack {:?} Exit: {:?}", [INFO] [stdout] 44 | | self.fun_name(), [INFO] [stdout] 45 | | self.counter, [INFO] [stdout] 46 | | self.data_stack, error); [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: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:72:25 [INFO] [stdout] | [INFO] [stdout] 72 | let (f, p, _) = try!(self.functions [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:86:26 [INFO] [stdout] | [INFO] [stdout] 86 | let (fun, pos) = try!(self.get_fun(function_pos)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:94:21 [INFO] [stdout] | [INFO] [stdout] 94 | let frame = try!(self.call_stack.pop().ok_or(Halted)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:96:26 [INFO] [stdout] | [INFO] [stdout] 96 | let (fun, pos) = try!(self.get_fun(frame.function_start)); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:123:19 [INFO] [stdout] | [INFO] [stdout] 123 | let top = try!(self.top()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:129:17 [INFO] [stdout] | [INFO] [stdout] 129 | let a = try!(self.pop()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:130:17 [INFO] [stdout] | [INFO] [stdout] 130 | let b = try!(self.pop()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:145:17 [INFO] [stdout] | [INFO] [stdout] 145 | let a = try!(self.top()); [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:148:34 [INFO] [stdout] | [INFO] [stdout] 148 | Equal => if a == 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:149:37 [INFO] [stdout] | [INFO] [stdout] 149 | NotEqual => if a != 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:150:39 [INFO] [stdout] | [INFO] [stdout] 150 | GreaterThan => if a > 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:151:36 [INFO] [stdout] | [INFO] [stdout] 151 | LessThan => if a < 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:152:41 [INFO] [stdout] | [INFO] [stdout] 152 | GreaterEqual => if a >= 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> src/vm/vm_run.rs:153:38 [INFO] [stdout] | [INFO] [stdout] 153 | LessEqual => if a <= 0 { try!(self.jump(offset)); }, [INFO] [stdout] | ^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.81s [INFO] running `Command { std: "docker" "inspect" "6a45eb88a1d0fe6b31c9a58165fe706b7214e6da15bd23224b075cf853199518", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6a45eb88a1d0fe6b31c9a58165fe706b7214e6da15bd23224b075cf853199518", kill_on_drop: false }` [INFO] [stdout] 6a45eb88a1d0fe6b31c9a58165fe706b7214e6da15bd23224b075cf853199518