[INFO] cloning repository https://github.com/polyfractal/Turbine
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/polyfractal/Turbine" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpolyfractal%2FTurbine", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpolyfractal%2FTurbine'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] d5c837956f4dfad7f4478cc02a2bafd98c77be14
[INFO] checking polyfractal/Turbine against try#93086cfebfccb79083c59d0d3b2052944bba643c for pr-146440-1
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpolyfractal%2FTurbine" "/workspace/builds/worker-3-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-3-tc2/source'...
[INFO] [stderr] done.
[INFO] started tweaking git repo https://github.com/polyfractal/Turbine
[INFO] finished tweaking git repo https://github.com/polyfractal/Turbine
[INFO] tweaked toml for git repo https://github.com/polyfractal/Turbine written to /workspace/builds/worker-3-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/polyfractal/Turbine on toolchain 93086cfebfccb79083c59d0d3b2052944bba643c
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/polyfractal/Turbine 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" "+93086cfebfccb79083c59d0d3b2052944bba643c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr] warning: Cargo.toml: `package.edition` is unspecified, defaulting to `2015` while the latest is `2024`
[INFO] [stderr] warning: `turbine` (manifest) generated 1 warning
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] a3cf044ae526109043e7376d11ce3e7529aa66ace7fd3c557ebb82901ac4a47a
[INFO] running `Command { std: "docker" "start" "-a" "a3cf044ae526109043e7376d11ce3e7529aa66ace7fd3c557ebb82901ac4a47a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "a3cf044ae526109043e7376d11ce3e7529aa66ace7fd3c557ebb82901ac4a47a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a3cf044ae526109043e7376d11ce3e7529aa66ace7fd3c557ebb82901ac4a47a", kill_on_drop: false }`
[INFO] [stdout] a3cf044ae526109043e7376d11ce3e7529aa66ace7fd3c557ebb82901ac4a47a
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-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:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 67d3009e4e538331a611142be7f30e999de093d9e08b372d804e72d6d050dfe8
[INFO] running `Command { std: "docker" "start" "-a" "67d3009e4e538331a611142be7f30e999de093d9e08b372d804e72d6d050dfe8", kill_on_drop: false }`
[INFO] [stderr] warning: Cargo.toml: `package.edition` is unspecified, defaulting to `2015` while the latest is `2024`
[INFO] [stderr] warning: `turbine` (manifest) generated 1 warning
[INFO] [stderr]    Compiling winapi-build v0.1.1
[INFO] [stderr]     Checking winapi v0.2.3
[INFO] [stderr]     Checking libc v0.1.10
[INFO] [stderr]     Checking log v0.3.2
[INFO] [stderr]    Compiling kernel32-sys v0.1.4
[INFO] [stderr]    Compiling advapi32-sys v0.1.2
[INFO] [stderr]     Checking rand v0.3.11
[INFO] [stderr]     Checking time v0.1.32
[INFO] [stderr]     Checking turbine v0.1.0 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0425]: cannot find function `atomic_store_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:130:42
[INFO] [stdout]     |
[INFO] [stdout] 130 |         Ordering::Release => intrinsics::atomic_store_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:141:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_store` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 130 -         Ordering::Release => intrinsics::atomic_store_rel(dst, val),
[INFO] [stdout] 130 +         Ordering::Release => intrinsics::atomic_store(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_store_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:131:42
[INFO] [stdout]     |
[INFO] [stdout] 131 |         Ordering::Relaxed => intrinsics::atomic_store_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_load_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:139:42
[INFO] [stdout]     |
[INFO] [stdout] 139 |         Ordering::Acquire => intrinsics::atomic_load_acq(dst),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:132:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_load` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 139 -         Ordering::Acquire => intrinsics::atomic_load_acq(dst),
[INFO] [stdout] 139 +         Ordering::Acquire => intrinsics::atomic_load(dst),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_load_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:140:42
[INFO] [stdout]     |
[INFO] [stdout] 140 |         Ordering::Relaxed => intrinsics::atomic_load_relaxed(dst),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:148:42
[INFO] [stdout]     |
[INFO] [stdout] 148 |         Ordering::Acquire => intrinsics::atomic_xchg_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 148 -         Ordering::Acquire => intrinsics::atomic_xchg_acq(dst, val),
[INFO] [stdout] 148 +         Ordering::Acquire => intrinsics::atomic_xchg(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:149:42
[INFO] [stdout]     |
[INFO] [stdout] 149 |         Ordering::Release => intrinsics::atomic_xchg_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 149 -         Ordering::Release => intrinsics::atomic_xchg_rel(dst, val),
[INFO] [stdout] 149 +         Ordering::Release => intrinsics::atomic_xchg(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:150:42
[INFO] [stdout]     |
[INFO] [stdout] 150 |         Ordering::AcqRel  => intrinsics::atomic_xchg_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:151:42
[INFO] [stdout]     |
[INFO] [stdout] 151 |         Ordering::Relaxed => intrinsics::atomic_xchg_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:160:42
[INFO] [stdout]     |
[INFO] [stdout] 160 |         Ordering::Acquire => intrinsics::atomic_xadd_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xadd` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 160 -         Ordering::Acquire => intrinsics::atomic_xadd_acq(dst, val),
[INFO] [stdout] 160 +         Ordering::Acquire => intrinsics::atomic_xadd(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:161:42
[INFO] [stdout]     |
[INFO] [stdout] 161 |         Ordering::Release => intrinsics::atomic_xadd_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xadd` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 161 -         Ordering::Release => intrinsics::atomic_xadd_rel(dst, val),
[INFO] [stdout] 161 +         Ordering::Release => intrinsics::atomic_xadd(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:162:42
[INFO] [stdout]     |
[INFO] [stdout] 162 |         Ordering::AcqRel  => intrinsics::atomic_xadd_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:163:42
[INFO] [stdout]     |
[INFO] [stdout] 163 |         Ordering::Relaxed => intrinsics::atomic_xadd_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:172:42
[INFO] [stdout]     |
[INFO] [stdout] 172 |         Ordering::Acquire => intrinsics::atomic_xsub_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xsub` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 172 -         Ordering::Acquire => intrinsics::atomic_xsub_acq(dst, val),
[INFO] [stdout] 172 +         Ordering::Acquire => intrinsics::atomic_xsub(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:173:42
[INFO] [stdout]     |
[INFO] [stdout] 173 |         Ordering::Release => intrinsics::atomic_xsub_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xsub` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 173 -         Ordering::Release => intrinsics::atomic_xsub_rel(dst, val),
[INFO] [stdout] 173 +         Ordering::Release => intrinsics::atomic_xsub(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:174:42
[INFO] [stdout]     |
[INFO] [stdout] 174 |         Ordering::AcqRel  => intrinsics::atomic_xsub_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:175:42
[INFO] [stdout]     |
[INFO] [stdout] 175 |         Ordering::Relaxed => intrinsics::atomic_xsub_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:183:42
[INFO] [stdout]     |
[INFO] [stdout] 183 |         Ordering::Acquire => intrinsics::atomic_cxchg_acq(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:105:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 183 -         Ordering::Acquire => intrinsics::atomic_cxchg_acq(dst, old, new),
[INFO] [stdout] 183 +         Ordering::Acquire => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:184:42
[INFO] [stdout]     |
[INFO] [stdout] 184 |         Ordering::Release => intrinsics::atomic_cxchg_rel(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:105:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 184 -         Ordering::Release => intrinsics::atomic_cxchg_rel(dst, old, new),
[INFO] [stdout] 184 +         Ordering::Release => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:185:42
[INFO] [stdout]     |
[INFO] [stdout] 185 |         Ordering::AcqRel  => intrinsics::atomic_cxchg_acqrel(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:186:42
[INFO] [stdout]     |
[INFO] [stdout] 186 |         Ordering::Relaxed => intrinsics::atomic_cxchg_relaxed(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:115:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:123:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchgweak` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 186 -         Ordering::Relaxed => intrinsics::atomic_cxchg_relaxed(dst, old, new),
[INFO] [stdout] 186 +         Ordering::Relaxed => intrinsics::atomic_cxchgweak(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:194:42
[INFO] [stdout]     |
[INFO] [stdout] 194 |         Ordering::Acquire => intrinsics::atomic_and_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_and` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 194 -         Ordering::Acquire => intrinsics::atomic_and_acq(dst, val),
[INFO] [stdout] 194 +         Ordering::Acquire => intrinsics::atomic_and(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:195:42
[INFO] [stdout]     |
[INFO] [stdout] 195 |         Ordering::Release => intrinsics::atomic_and_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_and` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 195 -         Ordering::Release => intrinsics::atomic_and_rel(dst, val),
[INFO] [stdout] 195 +         Ordering::Release => intrinsics::atomic_and(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:196:42
[INFO] [stdout]     |
[INFO] [stdout] 196 |         Ordering::AcqRel  => intrinsics::atomic_and_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:197:42
[INFO] [stdout]     |
[INFO] [stdout] 197 |         Ordering::Relaxed => intrinsics::atomic_and_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:205:42
[INFO] [stdout]     |
[INFO] [stdout] 205 |         Ordering::Acquire => intrinsics::atomic_nand_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_nand` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 205 -         Ordering::Acquire => intrinsics::atomic_nand_acq(dst, val),
[INFO] [stdout] 205 +         Ordering::Acquire => intrinsics::atomic_nand(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:206:42
[INFO] [stdout]     |
[INFO] [stdout] 206 |         Ordering::Release => intrinsics::atomic_nand_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_nand` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 206 -         Ordering::Release => intrinsics::atomic_nand_rel(dst, val),
[INFO] [stdout] 206 +         Ordering::Release => intrinsics::atomic_nand(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:207:42
[INFO] [stdout]     |
[INFO] [stdout] 207 |         Ordering::AcqRel  => intrinsics::atomic_nand_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:208:42
[INFO] [stdout]     |
[INFO] [stdout] 208 |         Ordering::Relaxed => intrinsics::atomic_nand_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:217:42
[INFO] [stdout]     |
[INFO] [stdout] 217 |         Ordering::Acquire => intrinsics::atomic_or_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_or` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 217 -         Ordering::Acquire => intrinsics::atomic_or_acq(dst, val),
[INFO] [stdout] 217 +         Ordering::Acquire => intrinsics::atomic_or(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:218:42
[INFO] [stdout]     |
[INFO] [stdout] 218 |         Ordering::Release => intrinsics::atomic_or_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_or` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 218 -         Ordering::Release => intrinsics::atomic_or_rel(dst, val),
[INFO] [stdout] 218 +         Ordering::Release => intrinsics::atomic_or(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:219:42
[INFO] [stdout]     |
[INFO] [stdout] 219 |         Ordering::AcqRel  => intrinsics::atomic_or_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:220:42
[INFO] [stdout]     |
[INFO] [stdout] 220 |         Ordering::Relaxed => intrinsics::atomic_or_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:229:42
[INFO] [stdout]     |
[INFO] [stdout] 229 |         Ordering::Acquire => intrinsics::atomic_xor_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xor` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 229 -         Ordering::Acquire => intrinsics::atomic_xor_acq(dst, val),
[INFO] [stdout] 229 +         Ordering::Acquire => intrinsics::atomic_xor(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:230:42
[INFO] [stdout]     |
[INFO] [stdout] 230 |         Ordering::Release => intrinsics::atomic_xor_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xor` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 230 -         Ordering::Release => intrinsics::atomic_xor_rel(dst, val),
[INFO] [stdout] 230 +         Ordering::Release => intrinsics::atomic_xor(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:231:42
[INFO] [stdout]     |
[INFO] [stdout] 231 |         Ordering::AcqRel  => intrinsics::atomic_xor_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:232:42
[INFO] [stdout]     |
[INFO] [stdout] 232 |         Ordering::Relaxed => intrinsics::atomic_xor_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `core_intrinsics` is internal to the compiler or standard library
[INFO] [stdout]  --> src/lib.rs:8:12
[INFO] [stdout]   |
[INFO] [stdout] 8 | #![feature(core_intrinsics)]
[INFO] [stdout]   |            ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: using it is strongly discouraged
[INFO] [stdout]   = note: `#[warn(internal_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 32 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0433]: cannot find `funcs` in `libc`
[INFO] [stdout]    --> src/lib.rs:407:15
[INFO] [stdout]     |
[INFO] [stdout] 407 |     use libc::funcs::posix88::unistd::usleep;
[INFO] [stdout]     |               ^^^^^ could not find `funcs` in `libc`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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: the feature `ptr_as_ref` has been stable since 1.9.0 and no longer requires an attribute to enable
[INFO] [stdout]  --> src/lib.rs:4:12
[INFO] [stdout]   |
[INFO] [stdout] 4 | #![feature(ptr_as_ref)]
[INFO] [stdout]   |            ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(stable_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `convert`
[INFO] [stdout]  --> src/lib.rs:6:12
[INFO] [stdout]   |
[INFO] [stdout] 6 | #![feature(convert)]
[INFO] [stdout]   |            ^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_store_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:130:42
[INFO] [stdout]     |
[INFO] [stdout] 130 |         Ordering::Release => intrinsics::atomic_store_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:141:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_store` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 130 -         Ordering::Release => intrinsics::atomic_store_rel(dst, val),
[INFO] [stdout] 130 +         Ordering::Release => intrinsics::atomic_store(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_store_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:131:42
[INFO] [stdout]     |
[INFO] [stdout] 131 |         Ordering::Relaxed => intrinsics::atomic_store_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_load_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:139:42
[INFO] [stdout]     |
[INFO] [stdout] 139 |         Ordering::Acquire => intrinsics::atomic_load_acq(dst),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:132:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_load` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 139 -         Ordering::Acquire => intrinsics::atomic_load_acq(dst),
[INFO] [stdout] 139 +         Ordering::Acquire => intrinsics::atomic_load(dst),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_load_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:140:42
[INFO] [stdout]     |
[INFO] [stdout] 140 |         Ordering::Relaxed => intrinsics::atomic_load_relaxed(dst),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:148:42
[INFO] [stdout]     |
[INFO] [stdout] 148 |         Ordering::Acquire => intrinsics::atomic_xchg_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 148 -         Ordering::Acquire => intrinsics::atomic_xchg_acq(dst, val),
[INFO] [stdout] 148 +         Ordering::Acquire => intrinsics::atomic_xchg(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:149:42
[INFO] [stdout]     |
[INFO] [stdout] 149 |         Ordering::Release => intrinsics::atomic_xchg_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 149 -         Ordering::Release => intrinsics::atomic_xchg_rel(dst, val),
[INFO] [stdout] 149 +         Ordering::Release => intrinsics::atomic_xchg(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:150:42
[INFO] [stdout]     |
[INFO] [stdout] 150 |         Ordering::AcqRel  => intrinsics::atomic_xchg_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xchg_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:151:42
[INFO] [stdout]     |
[INFO] [stdout] 151 |         Ordering::Relaxed => intrinsics::atomic_xchg_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:160:42
[INFO] [stdout]     |
[INFO] [stdout] 160 |         Ordering::Acquire => intrinsics::atomic_xadd_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xadd` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 160 -         Ordering::Acquire => intrinsics::atomic_xadd_acq(dst, val),
[INFO] [stdout] 160 +         Ordering::Acquire => intrinsics::atomic_xadd(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:161:42
[INFO] [stdout]     |
[INFO] [stdout] 161 |         Ordering::Release => intrinsics::atomic_xadd_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xadd` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 161 -         Ordering::Release => intrinsics::atomic_xadd_rel(dst, val),
[INFO] [stdout] 161 +         Ordering::Release => intrinsics::atomic_xadd(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:162:42
[INFO] [stdout]     |
[INFO] [stdout] 162 |         Ordering::AcqRel  => intrinsics::atomic_xadd_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xadd_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:163:42
[INFO] [stdout]     |
[INFO] [stdout] 163 |         Ordering::Relaxed => intrinsics::atomic_xadd_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:172:42
[INFO] [stdout]     |
[INFO] [stdout] 172 |         Ordering::Acquire => intrinsics::atomic_xsub_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xsub` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 172 -         Ordering::Acquire => intrinsics::atomic_xsub_acq(dst, val),
[INFO] [stdout] 172 +         Ordering::Acquire => intrinsics::atomic_xsub(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:173:42
[INFO] [stdout]     |
[INFO] [stdout] 173 |         Ordering::Release => intrinsics::atomic_xsub_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xsub` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 173 -         Ordering::Release => intrinsics::atomic_xsub_rel(dst, val),
[INFO] [stdout] 173 +         Ordering::Release => intrinsics::atomic_xsub(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:174:42
[INFO] [stdout]     |
[INFO] [stdout] 174 |         Ordering::AcqRel  => intrinsics::atomic_xsub_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xsub_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:175:42
[INFO] [stdout]     |
[INFO] [stdout] 175 |         Ordering::Relaxed => intrinsics::atomic_xsub_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:183:42
[INFO] [stdout]     |
[INFO] [stdout] 183 |         Ordering::Acquire => intrinsics::atomic_cxchg_acq(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:105:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 183 -         Ordering::Acquire => intrinsics::atomic_cxchg_acq(dst, old, new),
[INFO] [stdout] 183 +         Ordering::Acquire => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:184:42
[INFO] [stdout]     |
[INFO] [stdout] 184 |         Ordering::Release => intrinsics::atomic_cxchg_rel(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:105:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchg` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 184 -         Ordering::Release => intrinsics::atomic_cxchg_rel(dst, old, new),
[INFO] [stdout] 184 +         Ordering::Release => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:185:42
[INFO] [stdout]     |
[INFO] [stdout] 185 |         Ordering::AcqRel  => intrinsics::atomic_cxchg_acqrel(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_cxchg_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:186:42
[INFO] [stdout]     |
[INFO] [stdout] 186 |         Ordering::Relaxed => intrinsics::atomic_cxchg_relaxed(dst, old, new),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:115:0
[INFO] [stdout]    ::: /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:123:15
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_cxchgweak` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 186 -         Ordering::Relaxed => intrinsics::atomic_cxchg_relaxed(dst, old, new),
[INFO] [stdout] 186 +         Ordering::Relaxed => intrinsics::atomic_cxchgweak(dst, old, new),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:194:42
[INFO] [stdout]     |
[INFO] [stdout] 194 |         Ordering::Acquire => intrinsics::atomic_and_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_and` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 194 -         Ordering::Acquire => intrinsics::atomic_and_acq(dst, val),
[INFO] [stdout] 194 +         Ordering::Acquire => intrinsics::atomic_and(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:195:42
[INFO] [stdout]     |
[INFO] [stdout] 195 |         Ordering::Release => intrinsics::atomic_and_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_and` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 195 -         Ordering::Release => intrinsics::atomic_and_rel(dst, val),
[INFO] [stdout] 195 +         Ordering::Release => intrinsics::atomic_and(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:196:42
[INFO] [stdout]     |
[INFO] [stdout] 196 |         Ordering::AcqRel  => intrinsics::atomic_and_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_and_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:197:42
[INFO] [stdout]     |
[INFO] [stdout] 197 |         Ordering::Relaxed => intrinsics::atomic_and_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:205:42
[INFO] [stdout]     |
[INFO] [stdout] 205 |         Ordering::Acquire => intrinsics::atomic_nand_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_nand` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 205 -         Ordering::Acquire => intrinsics::atomic_nand_acq(dst, val),
[INFO] [stdout] 205 +         Ordering::Acquire => intrinsics::atomic_nand(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:206:42
[INFO] [stdout]     |
[INFO] [stdout] 206 |         Ordering::Release => intrinsics::atomic_nand_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_nand` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 206 -         Ordering::Release => intrinsics::atomic_nand_rel(dst, val),
[INFO] [stdout] 206 +         Ordering::Release => intrinsics::atomic_nand(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:207:42
[INFO] [stdout]     |
[INFO] [stdout] 207 |         Ordering::AcqRel  => intrinsics::atomic_nand_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_nand_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:208:42
[INFO] [stdout]     |
[INFO] [stdout] 208 |         Ordering::Relaxed => intrinsics::atomic_nand_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:217:42
[INFO] [stdout]     |
[INFO] [stdout] 217 |         Ordering::Acquire => intrinsics::atomic_or_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_or` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 217 -         Ordering::Acquire => intrinsics::atomic_or_acq(dst, val),
[INFO] [stdout] 217 +         Ordering::Acquire => intrinsics::atomic_or(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:218:42
[INFO] [stdout]     |
[INFO] [stdout] 218 |         Ordering::Release => intrinsics::atomic_or_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_or` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 218 -         Ordering::Release => intrinsics::atomic_or_rel(dst, val),
[INFO] [stdout] 218 +         Ordering::Release => intrinsics::atomic_or(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:219:42
[INFO] [stdout]     |
[INFO] [stdout] 219 |         Ordering::AcqRel  => intrinsics::atomic_or_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_or_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:220:42
[INFO] [stdout]     |
[INFO] [stdout] 220 |         Ordering::Relaxed => intrinsics::atomic_or_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_acq` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:229:42
[INFO] [stdout]     |
[INFO] [stdout] 229 |         Ordering::Acquire => intrinsics::atomic_xor_acq(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xor` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 229 -         Ordering::Acquire => intrinsics::atomic_xor_acq(dst, val),
[INFO] [stdout] 229 +         Ordering::Acquire => intrinsics::atomic_xor(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_rel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:230:42
[INFO] [stdout]     |
[INFO] [stdout] 230 |         Ordering::Release => intrinsics::atomic_xor_rel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named function `atomic_xor` defined here
[INFO] [stdout] help: a function with a similar name exists
[INFO] [stdout]     |
[INFO] [stdout] 230 -         Ordering::Release => intrinsics::atomic_xor_rel(dst, val),
[INFO] [stdout] 230 +         Ordering::Release => intrinsics::atomic_xor(dst, val),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_acqrel` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:231:42
[INFO] [stdout]     |
[INFO] [stdout] 231 |         Ordering::AcqRel  => intrinsics::atomic_xor_acqrel(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `atomic_xor_relaxed` in module `intrinsics`
[INFO] [stdout]    --> src/atomicnum.rs:232:42
[INFO] [stdout]     |
[INFO] [stdout] 232 |         Ordering::Relaxed => intrinsics::atomic_xor_relaxed(dst, val),
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^^ not found in `intrinsics`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `core_intrinsics` is internal to the compiler or standard library
[INFO] [stdout]  --> src/lib.rs:8:12
[INFO] [stdout]   |
[INFO] [stdout] 8 | #![feature(core_intrinsics)]
[INFO] [stdout]   |            ^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: using it is strongly discouraged
[INFO] [stdout]   = note: `#[warn(internal_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[INFO] [stdout]    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 32 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:80:13
[INFO] [stdout]    |
[INFO] [stdout] 80 |             debug!("              Current: {}, waiting on: {}", internal_cursor, internal_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:132:14
[INFO] [stdout]     |
[INFO] [stdout] 132 |         _ => intrinsics::atomic_store(dst, val)
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_store`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:141:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 128 | unsafe fn atomic_store<T: std::marker::Copy>(dst: *mut T, val: T, order:Ordering) {
[INFO] [stdout]     |                         +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:83:13
[INFO] [stdout]    |
[INFO] [stdout] 83 |             debug!("                            Available: {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:141:38
[INFO] [stdout]     |
[INFO] [stdout] 141 |         _ => intrinsics::atomic_load(dst)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_load`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:132:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 137 | unsafe fn atomic_load<T: std::marker::Copy>(dst: *const T, order:Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:152:14
[INFO] [stdout]     |
[INFO] [stdout] 152 |         _ => intrinsics::atomic_xchg(dst, val)
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xchg`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 146 | unsafe fn atomic_swap<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:164:38
[INFO] [stdout]     |
[INFO] [stdout] 164 |         _ => intrinsics::atomic_xadd(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xadd`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 158 | unsafe fn atomic_add<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:88:13
[INFO] [stdout]    |
[INFO] [stdout] 88 |             debug!("              from: {}, to: {} -- {}", from, to, (to < from));
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:164:43
[INFO] [stdout]     |
[INFO] [stdout] 164 |         _ => intrinsics::atomic_xadd(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xadd`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 158 | unsafe fn atomic_add<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:176:38
[INFO] [stdout]     |
[INFO] [stdout] 176 |         _ => intrinsics::atomic_xsub(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xsub`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 170 | unsafe fn atomic_sub<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:176:43
[INFO] [stdout]     |
[INFO] [stdout] 176 |         _ => intrinsics::atomic_xsub(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xsub`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 170 | unsafe fn atomic_sub<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:90:17
[INFO] [stdout]    |
[INFO] [stdout] 90 |                 debug!("                        ROLLOVER");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:187:14
[INFO] [stdout]     |
[INFO] [stdout] 187 |         _ => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_cxchg`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 181 | unsafe fn atomic_compare_and_swap<T: std::marker::Copy>(dst: *mut T, old:T, new:T, order: Ordering) -> T {
[INFO] [stdout]     |                                    +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:198:37
[INFO] [stdout]     |
[INFO] [stdout] 198 |         _ => intrinsics::atomic_and(dst, val)
[INFO] [stdout]     |              ---------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_and`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 192 | unsafe fn atomic_and<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:198:42
[INFO] [stdout]     |
[INFO] [stdout] 198 |         _ => intrinsics::atomic_and(dst, val)
[INFO] [stdout]     |              ----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_and`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 192 | unsafe fn atomic_and<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:95:17
[INFO] [stdout]    |
[INFO] [stdout] 95 |                 debug!("                        ROLLOVER (total) -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:209:38
[INFO] [stdout]     |
[INFO] [stdout] 209 |         _ => intrinsics::atomic_nand(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_nand`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 203 | unsafe fn atomic_nand<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:209:43
[INFO] [stdout]     |
[INFO] [stdout] 209 |         _ => intrinsics::atomic_nand(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_nand`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 203 | unsafe fn atomic_nand<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:221:36
[INFO] [stdout]     |
[INFO] [stdout] 221 |         _ => intrinsics::atomic_or(dst, val)
[INFO] [stdout]     |              --------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_or`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 215 | unsafe fn atomic_or<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                      +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:221:41
[INFO] [stdout]     |
[INFO] [stdout] 221 |         _ => intrinsics::atomic_or(dst, val)
[INFO] [stdout]     |              ---------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_or`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 215 | unsafe fn atomic_or<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                      +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]   --> src/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:99:17
[INFO] [stdout]    |
[INFO] [stdout] 99 |                 debug!("                        WTF to == from    -- ({} == {}) && ({} < {})", to, from, internal_cursor, available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:233:37
[INFO] [stdout]     |
[INFO] [stdout] 233 |         _ => intrinsics::atomic_xor(dst, val)
[INFO] [stdout]     |              ---------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_xor`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 227 | unsafe fn atomic_xor<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:233:42
[INFO] [stdout]     |
[INFO] [stdout] 233 |         _ => intrinsics::atomic_xor(dst, val)
[INFO] [stdout]     |              ----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_xor`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 227 | unsafe fn atomic_xor<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:103:13
[INFO] [stdout]     |
[INFO] [stdout] 103 |             debug!("              Post-modification from: {}, to: {} -- {}", from, to, (to < from));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:115:17
[INFO] [stdout]     |
[INFO] [stdout] 115 |                 debug!("ROlLOVER GET");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:125:13
[INFO] [stdout]     |
[INFO] [stdout] 125 |             debug!("                    Finished processing event.  Cursor @ {} ({})", available, available & mask);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/eventprocessor.rs:133:9
[INFO] [stdout]     |
[INFO] [stdout] 133 |         debug!("BusyWait::end");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:39:13
[INFO] [stdout]    |
[INFO] [stdout] 39 |             debug!("                    cursor: {}", cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:42:17
[INFO] [stdout]    |
[INFO] [stdout] 42 |                 debug!("                    Same as dep cursor, abort!");
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:46:13
[INFO] [stdout]    |
[INFO] [stdout] 46 |             debug!("                    dep cursor: {}, ring_size: {}, sequence: {}", cursor, self.ring_size as isize, sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:47:13
[INFO] [stdout]    |
[INFO] [stdout] 47 |             debug!("                    min_cursor: {}", min_cursor);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:67:9
[INFO] [stdout]    |
[INFO] [stdout] 67 |         debug!("                    Waiting for: {}", sequence);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/waitstrategy.rs:77:9
[INFO] [stdout]    |
[INFO] [stdout] 77 |         debug!("                    Wait done, returning {}", available);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/ringbuffer.rs:74:9
[INFO] [stdout]    |
[INFO] [stdout] 74 |         debug!("              RingBuffer get({}, {})", from, size);
[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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:358:9
[INFO] [stdout]     |
[INFO] [stdout] 358 |         debug!("current_pos is {}, writing to {}", self.current_pos, write_pos);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:365:9
[INFO] [stdout]     |
[INFO] [stdout] 365 |         debug!("Write complete.")
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:378:9
[INFO] [stdout]     |
[INFO] [stdout] 378 | ...   debug!("{} == {} ({} & {})  -- {}", self.until, self.current_pos & self.mask, self.current_pos, self.mask, self.until == (self.current_pos & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:381:13
[INFO] [stdout]     |
[INFO] [stdout] 381 |             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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:385:17
[INFO] [stdout]     |
[INFO] [stdout] 385 |                 debug!("CURSOR: {}", v.load());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:390:21
[INFO] [stdout]     |
[INFO] [stdout] 390 | ...   debug!("Not writeable!  {} - {} == {}, which is >= {}", self.current_pos, min_cursor, (self.current_pos - min_cursor), self.size);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:397:13
[INFO] [stdout]     |
[INFO] [stdout] 397 |             debug!("current_pos: {}, min_cursor: {}, new until: {}", self.current_pos, min_cursor, self.until);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:398:13
[INFO] [stdout]     |
[INFO] [stdout] 398 |             debug!("current_pos & mask: {}, min_cursor & mask: {}", (self.current_pos & self.mask), (min_cursor & self.mask));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:682:21
[INFO] [stdout]     |
[INFO] [stdout] 682 |                     debug!("EP:: last: {}, value: {}", last, x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:682:21
[INFO] [stdout]     |
[INFO] [stdout] 682 |                     debug!("EP:: last: {}, value: {}", last, x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:682:21
[INFO] [stdout]     |
[INFO] [stdout] 682 |                     debug!("EP:: last: {}, value: {}", last, x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:682:21
[INFO] [stdout]     |
[INFO] [stdout] 682 |                     debug!("EP:: last: {}, value: {}", last, x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:682:21
[INFO] [stdout]     |
[INFO] [stdout] 682 |                     debug!("EP:: last: {}, value: {}", last, x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:686:21
[INFO] [stdout]     |
[INFO] [stdout] 686 |                     debug!("EP::counter: {}", counter.load(Ordering::SeqCst));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:686:21
[INFO] [stdout]     |
[INFO] [stdout] 686 |                     debug!("EP::counter: {}", counter.load(Ordering::SeqCst));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:686:21
[INFO] [stdout]     |
[INFO] [stdout] 686 |                     debug!("EP::counter: {}", counter.load(Ordering::SeqCst));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:686:21
[INFO] [stdout]     |
[INFO] [stdout] 686 |                     debug!("EP::counter: {}", counter.load(Ordering::SeqCst));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:686:21
[INFO] [stdout]     |
[INFO] [stdout] 686 |                     debug!("EP::counter: {}", counter.load(Ordering::SeqCst));
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:704:13
[INFO] [stdout]     |
[INFO] [stdout] 704 |             debug!("Writing: {}", x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:704:13
[INFO] [stdout]     |
[INFO] [stdout] 704 |             debug!("Writing: {}", x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:704:13
[INFO] [stdout]     |
[INFO] [stdout] 704 |             debug!("Writing: {}", x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:704:13
[INFO] [stdout]     |
[INFO] [stdout] 704 |             debug!("Writing: {}", x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:704:13
[INFO] [stdout]     |
[INFO] [stdout] 704 |             debug!("Writing: {}", x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:726:21
[INFO] [stdout]     |
[INFO] [stdout] 726 |                     debug!(">>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:726:21
[INFO] [stdout]     |
[INFO] [stdout] 726 |                     debug!(">>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:726:21
[INFO] [stdout]     |
[INFO] [stdout] 726 |                     debug!(">>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:726:21
[INFO] [stdout]     |
[INFO] [stdout] 726 |                     debug!(">>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:726:21
[INFO] [stdout]     |
[INFO] [stdout] 726 |                     debug!(">>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:730:21
[INFO] [stdout]     |
[INFO] [stdout] 730 |                     debug!("EP::counter: {}", counter);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:730:21
[INFO] [stdout]     |
[INFO] [stdout] 730 |                     debug!("EP::counter: {}", counter);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:730:21
[INFO] [stdout]     |
[INFO] [stdout] 730 |                     debug!("EP::counter: {}", counter);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:730:21
[INFO] [stdout]     |
[INFO] [stdout] 730 |                     debug!("EP::counter: {}", counter);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:730:21
[INFO] [stdout]     |
[INFO] [stdout] 730 |                     debug!("EP::counter: {}", counter);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:746:13
[INFO] [stdout]     |
[INFO] [stdout] 746 |             debug!("______Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:746:13
[INFO] [stdout]     |
[INFO] [stdout] 746 |             debug!("______Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:746:13
[INFO] [stdout]     |
[INFO] [stdout] 746 |             debug!("______Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:746:13
[INFO] [stdout]     |
[INFO] [stdout] 746 |             debug!("______Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:746:13
[INFO] [stdout]     |
[INFO] [stdout] 746 |             debug!("______Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:770:21
[INFO] [stdout]     |
[INFO] [stdout] 770 |                     debug!(">>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:770:21
[INFO] [stdout]     |
[INFO] [stdout] 770 |                     debug!(">>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:770:21
[INFO] [stdout]     |
[INFO] [stdout] 770 |                     debug!(">>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:770:21
[INFO] [stdout]     |
[INFO] [stdout] 770 |                     debug!(">>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:770:21
[INFO] [stdout]     |
[INFO] [stdout] 770 |                     debug!(">>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:784:13
[INFO] [stdout]     |
[INFO] [stdout] 784 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:784:13
[INFO] [stdout]     |
[INFO] [stdout] 784 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:784:13
[INFO] [stdout]     |
[INFO] [stdout] 784 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:784:13
[INFO] [stdout]     |
[INFO] [stdout] 784 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:784:13
[INFO] [stdout]     |
[INFO] [stdout] 784 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:792:13
[INFO] [stdout]     |
[INFO] [stdout] 792 |             debug!("Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:792:13
[INFO] [stdout]     |
[INFO] [stdout] 792 |             debug!("Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:792:13
[INFO] [stdout]     |
[INFO] [stdout] 792 |             debug!("Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:792:13
[INFO] [stdout]     |
[INFO] [stdout] 792 |             debug!("Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:792:13
[INFO] [stdout]     |
[INFO] [stdout] 792 |             debug!("Writing {}", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:796:9
[INFO] [stdout]     |
[INFO] [stdout] 796 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:796:9
[INFO] [stdout]     |
[INFO] [stdout] 796 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:796:9
[INFO] [stdout]     |
[INFO] [stdout] 796 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:796:9
[INFO] [stdout]     |
[INFO] [stdout] 796 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:796:9
[INFO] [stdout]     |
[INFO] [stdout] 796 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:798:9
[INFO] [stdout]     |
[INFO] [stdout] 798 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:798:9
[INFO] [stdout]     |
[INFO] [stdout] 798 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:798:9
[INFO] [stdout]     |
[INFO] [stdout] 798 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:798:9
[INFO] [stdout]     |
[INFO] [stdout] 798 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:798:9
[INFO] [stdout]     |
[INFO] [stdout] 798 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:819:17
[INFO] [stdout]     |
[INFO] [stdout] 819 | ...   debug!("                                                SLEEPING {}s {}ns", sleep_time.as_secs(), sleep_time.subsec_nanos());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:819:17
[INFO] [stdout]     |
[INFO] [stdout] 819 | ...   debug!("                                                SLEEPING {}s {}ns", sleep_time.as_secs(), sleep_time.subsec_nanos());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:819:17
[INFO] [stdout]     |
[INFO] [stdout] 819 | ...   debug!("                                                SLEEPING {}s {}ns", sleep_time.as_secs(), sleep_time.subsec_nanos());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:819:17
[INFO] [stdout]     |
[INFO] [stdout] 819 | ...   debug!("                                                SLEEPING {}s {}ns", sleep_time.as_secs(), sleep_time.subsec_nanos());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:819:17
[INFO] [stdout]     |
[INFO] [stdout] 819 | ...   debug!("                                                SLEEPING {}s {}ns", sleep_time.as_secs(), sleep_time.subsec_nanos());
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] Some errors have detailed explanations: E0277, E0425, E0635.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/lib.rs:821:17
[INFO] [stdout]     |
[INFO] [stdout] 821 |                 debug!("                                                DONE SLEEPING");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:821:17
[INFO] [stdout]     |
[INFO] [stdout] 821 |                 debug!("                                                DONE SLEEPING");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:821:17
[INFO] [stdout]     |
[INFO] [stdout] 821 |                 debug!("                                                DONE SLEEPING");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:821:17
[INFO] [stdout]     |
[INFO] [stdout] 821 |                 debug!("                                                DONE SLEEPING");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:821:17
[INFO] [stdout]     |
[INFO] [stdout] 821 |                 debug!("                                                DONE SLEEPING");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:824:21
[INFO] [stdout]     |
[INFO] [stdout] 824 | ...   debug!("                                    >>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:824:21
[INFO] [stdout]     |
[INFO] [stdout] 824 | ...   debug!("                                    >>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:824:21
[INFO] [stdout]     |
[INFO] [stdout] 824 | ...   debug!("                                    >>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:824:21
[INFO] [stdout]     |
[INFO] [stdout] 824 | ...   debug!("                                    >>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:824:21
[INFO] [stdout]     |
[INFO] [stdout] 824 | ...   debug!("                                    >>>>>>>>>>>>>>>>>>>> last: {}, value: {}, -- {}", last, x.value, last + 1 == x.value);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:838:13
[INFO] [stdout]     |
[INFO] [stdout] 838 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:838:13
[INFO] [stdout]     |
[INFO] [stdout] 838 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] [stderr] error: could not compile `turbine` (lib) due to 53 previous errors; 127 warnings emitted
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/lib.rs:838:13
[INFO] [stdout]     |
[INFO] [stdout] 838 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] warning: unexpected `cfg` condition name: `log_level`
[INFO] [stdout]    --> src/lib.rs:838:13
[INFO] [stdout]     |
[INFO] [stdout] 838 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:838:13
[INFO] [stdout]     |
[INFO] [stdout] 838 |             debug!("Event processor done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:846:13
[INFO] [stdout]     |
[INFO] [stdout] 846 |             debug!("Writing {} -----------------------------------------------------", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:846:13
[INFO] [stdout]     |
[INFO] [stdout] 846 |             debug!("Writing {} -----------------------------------------------------", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:846:13
[INFO] [stdout]     |
[INFO] [stdout] 846 |             debug!("Writing {} -----------------------------------------------------", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:846:13
[INFO] [stdout]     |
[INFO] [stdout] 846 |             debug!("Writing {} -----------------------------------------------------", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:846:13
[INFO] [stdout]     |
[INFO] [stdout] 846 |             debug!("Writing {} -----------------------------------------------------", i);
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:850:9
[INFO] [stdout]     |
[INFO] [stdout] 850 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:850:9
[INFO] [stdout]     |
[INFO] [stdout] 850 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:850:9
[INFO] [stdout]     |
[INFO] [stdout] 850 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:850:9
[INFO] [stdout]     |
[INFO] [stdout] 850 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:850:9
[INFO] [stdout]     |
[INFO] [stdout] 850 |         debug!("Exit write loop");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:852:9
[INFO] [stdout]     |
[INFO] [stdout] 852 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:852:9
[INFO] [stdout]     |
[INFO] [stdout] 852 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:852:9
[INFO] [stdout]     |
[INFO] [stdout] 852 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:852:9
[INFO] [stdout]     |
[INFO] [stdout] 852 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:852:9
[INFO] [stdout]     |
[INFO] [stdout] 852 |         debug!("Recv_opt done");
[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]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1019:9
[INFO] [stdout]      |
[INFO] [stdout] 1019 |         error!("Channel: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1019:9
[INFO] [stdout]      |
[INFO] [stdout] 1019 |         error!("Channel: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1019:9
[INFO] [stdout]      |
[INFO] [stdout] 1019 |         error!("Channel: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1019:9
[INFO] [stdout]      |
[INFO] [stdout] 1019 |         error!("Channel: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1019:9
[INFO] [stdout]      |
[INFO] [stdout] 1019 |         error!("Channel: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1020:9
[INFO] [stdout]      |
[INFO] [stdout] 1020 |         error!("Channel: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1020:9
[INFO] [stdout]      |
[INFO] [stdout] 1020 |         error!("Channel: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1020:9
[INFO] [stdout]      |
[INFO] [stdout] 1020 |         error!("Channel: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1020:9
[INFO] [stdout]      |
[INFO] [stdout] 1020 |         error!("Channel: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1020:9
[INFO] [stdout]      |
[INFO] [stdout] 1020 |         error!("Channel: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1059:9
[INFO] [stdout]      |
[INFO] [stdout] 1059 |         error!("Turbine: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1059:9
[INFO] [stdout]      |
[INFO] [stdout] 1059 |         error!("Turbine: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1059:9
[INFO] [stdout]      |
[INFO] [stdout] 1059 |         error!("Turbine: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1059:9
[INFO] [stdout]      |
[INFO] [stdout] 1059 |         error!("Turbine: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1059:9
[INFO] [stdout]      |
[INFO] [stdout] 1059 |         error!("Turbine: Total time: {}", (end-start) as f32 / 1000000f32);
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1060:9
[INFO] [stdout]      |
[INFO] [stdout] 1060 |         error!("Turbine: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1060:9
[INFO] [stdout]      |
[INFO] [stdout] 1060 |         error!("Turbine: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1060:9
[INFO] [stdout]      |
[INFO] [stdout] 1060 |         error!("Turbine: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1060:9
[INFO] [stdout]      |
[INFO] [stdout] 1060 |         error!("Turbine: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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/lib.rs:1060:9
[INFO] [stdout]      |
[INFO] [stdout] 1060 |         error!("Turbine: ops/s: {}", 10000000f32 / ((end-start) as f32 / 1000000f32 / 1000f32));
[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]      = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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] error[E0658]: use of unstable library feature `rustc_private`: this crate is being loaded from the sysroot, an unstable location; did you mean to load this crate from crates.io via `Cargo.toml` instead?
[INFO] [stdout]   --> src/lib.rs:82:14
[INFO] [stdout]    |
[INFO] [stdout] 82 | #[cfg(test)] extern crate libc;
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: see issue #27812 <https://github.com/rust-lang/rust/issues/27812> for more information
[INFO] [stdout]    = help: add `#![feature(rustc_private)]` to the crate attributes to enable
[INFO] [stdout]    = note: this compiler was built on 2026-05-31; consider upgrading it if it is out of date
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `ptr_as_ref` has been stable since 1.9.0 and no longer requires an attribute to enable
[INFO] [stdout]  --> src/lib.rs:4:12
[INFO] [stdout]   |
[INFO] [stdout] 4 | #![feature(ptr_as_ref)]
[INFO] [stdout]   |            ^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(stable_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0635]: unknown feature `convert`
[INFO] [stdout]  --> src/lib.rs:6:12
[INFO] [stdout]   |
[INFO] [stdout] 6 | #![feature(convert)]
[INFO] [stdout]   |            ^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:132:14
[INFO] [stdout]     |
[INFO] [stdout] 132 |         _ => intrinsics::atomic_store(dst, val)
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_store`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:141:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 128 | unsafe fn atomic_store<T: std::marker::Copy>(dst: *mut T, val: T, order:Ordering) {
[INFO] [stdout]     |                         +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:141:38
[INFO] [stdout]     |
[INFO] [stdout] 141 |         _ => intrinsics::atomic_load(dst)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_load`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:132:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 137 | unsafe fn atomic_load<T: std::marker::Copy>(dst: *const T, order:Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:152:14
[INFO] [stdout]     |
[INFO] [stdout] 152 |         _ => intrinsics::atomic_xchg(dst, val)
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xchg`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:150:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 146 | unsafe fn atomic_swap<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:164:38
[INFO] [stdout]     |
[INFO] [stdout] 164 |         _ => intrinsics::atomic_xadd(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xadd`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 158 | unsafe fn atomic_add<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:164:43
[INFO] [stdout]     |
[INFO] [stdout] 164 |         _ => intrinsics::atomic_xadd(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xadd`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:160:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 158 | unsafe fn atomic_add<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:176:38
[INFO] [stdout]     |
[INFO] [stdout] 176 |         _ => intrinsics::atomic_xsub(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xsub`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 170 | unsafe fn atomic_sub<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:176:43
[INFO] [stdout]     |
[INFO] [stdout] 176 |         _ => intrinsics::atomic_xsub(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_xsub`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:170:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 170 | unsafe fn atomic_sub<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:187:14
[INFO] [stdout]     |
[INFO] [stdout] 187 |         _ => intrinsics::atomic_cxchg(dst, old, new),
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `atomic_cxchg`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:97:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 181 | unsafe fn atomic_compare_and_swap<T: std::marker::Copy>(dst: *mut T, old:T, new:T, order: Ordering) -> T {
[INFO] [stdout]     |                                    +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:198:37
[INFO] [stdout]     |
[INFO] [stdout] 198 |         _ => intrinsics::atomic_and(dst, val)
[INFO] [stdout]     |              ---------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_and`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 192 | unsafe fn atomic_and<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:198:42
[INFO] [stdout]     |
[INFO] [stdout] 198 |         _ => intrinsics::atomic_and(dst, val)
[INFO] [stdout]     |              ----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_and`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:180:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 192 | unsafe fn atomic_and<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:209:38
[INFO] [stdout]     |
[INFO] [stdout] 209 |         _ => intrinsics::atomic_nand(dst, val)
[INFO] [stdout]     |              ----------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_nand`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 203 | unsafe fn atomic_nand<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:209:43
[INFO] [stdout]     |
[INFO] [stdout] 209 |         _ => intrinsics::atomic_nand(dst, val)
[INFO] [stdout]     |              -----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_nand`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:190:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 203 | unsafe fn atomic_nand<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                        +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:221:36
[INFO] [stdout]     |
[INFO] [stdout] 221 |         _ => intrinsics::atomic_or(dst, val)
[INFO] [stdout]     |              --------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_or`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 215 | unsafe fn atomic_or<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                      +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:221:41
[INFO] [stdout]     |
[INFO] [stdout] 221 |         _ => intrinsics::atomic_or(dst, val)
[INFO] [stdout]     |              ---------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_or`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:200:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 215 | unsafe fn atomic_or<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                      +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:233:37
[INFO] [stdout]     |
[INFO] [stdout] 233 |         _ => intrinsics::atomic_xor(dst, val)
[INFO] [stdout]     |              ---------------------- ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_xor`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 227 | unsafe fn atomic_xor<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0277]: the trait bound `T: Copy` is not satisfied
[INFO] [stdout]    --> src/atomicnum.rs:233:42
[INFO] [stdout]     |
[INFO] [stdout] 233 |         _ => intrinsics::atomic_xor(dst, val)
[INFO] [stdout]     |              ----------------------      ^^^ the trait `Copy` is not implemented for `T`
[INFO] [stdout]     |              |
[INFO] [stdout]     |              required by a bound introduced by this call
[INFO] [stdout]     |
[INFO] [stdout] note: required by a bound in `std::intrinsics::atomic_xor`
[INFO] [stdout]    --> /rustc/93086cfebfccb79083c59d0d3b2052944bba643c/library/core/src/intrinsics/mod.rs:210:0
[INFO] [stdout] help: consider restricting type parameter `T` with trait `Copy`
[INFO] [stdout]     |
[INFO] [stdout] 227 | unsafe fn atomic_xor<T: std::marker::Copy>(dst: *mut T, val: T, order: Ordering) -> T {
[INFO] [stdout]     |                       +++++++++++++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0277, E0425, E0433, E0635, E0658.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0277`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `turbine` (lib test) due to 55 previous errors; 237 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "67d3009e4e538331a611142be7f30e999de093d9e08b372d804e72d6d050dfe8", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "67d3009e4e538331a611142be7f30e999de093d9e08b372d804e72d6d050dfe8", kill_on_drop: false }`
[INFO] [stdout] 67d3009e4e538331a611142be7f30e999de093d9e08b372d804e72d6d050dfe8
