[INFO] fetching crate ape-mbr 0.1.1... [INFO] testing ape-mbr-0.1.1 against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] extracting crate ape-mbr 0.1.1 into /workspace/builds/worker-7-tc1/source [INFO] started tweaking crates.io crate ape-mbr 0.1.1 [INFO] finished tweaking crates.io crate ape-mbr 0.1.1 [INFO] tweaked toml for crates.io crate ape-mbr 0.1.1 written to /workspace/builds/worker-7-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate ape-mbr 0.1.1 on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 48 packages to latest compatible versions [INFO] [stderr] Adding ape-fatfs v0.1.0 (available: v0.2.0) [INFO] [stderr] Adding embedded-io v0.4.0 (available: v0.6.1) [INFO] [stderr] Adding num_enum v0.6.1 (available: v0.7.4) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded ape-fatfs v0.1.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] ecb08fe76074c6de9e511d2499c2def703cd73915f10351ab127d78a3c7738d1 [INFO] running `Command { std: "docker" "start" "-a" "ecb08fe76074c6de9e511d2499c2def703cd73915f10351ab127d78a3c7738d1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "ecb08fe76074c6de9e511d2499c2def703cd73915f10351ab127d78a3c7738d1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ecb08fe76074c6de9e511d2499c2def703cd73915f10351ab127d78a3c7738d1", kill_on_drop: false }` [INFO] [stdout] ecb08fe76074c6de9e511d2499c2def703cd73915f10351ab127d78a3c7738d1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] d6fdd3c5c062693e85694e6c012712072e6978683b0d6f90c9272bd9764c6b6d [INFO] running `Command { std: "docker" "start" "-a" "d6fdd3c5c062693e85694e6c012712072e6978683b0d6f90c9272bd9764c6b6d", kill_on_drop: false }` [INFO] [stderr] Compiling embedded-io v0.4.0 [INFO] [stderr] Compiling syn v2.0.104 [INFO] [stderr] Compiling num_enum_derive v0.6.1 [INFO] [stderr] Compiling num_enum v0.6.1 [INFO] [stderr] Compiling ape-mbr v0.1.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:296:26 [INFO] [stdout] | [INFO] [stdout] 296 | pub fn get_partition(&mut self, id: PartitionId) -> Result, IO::Error> { [INFO] [stdout] | ^^^^^^^^^ ------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 296 | pub fn get_partition(&mut self, id: PartitionId) -> Result, IO::Error> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 3.72s [INFO] running `Command { std: "docker" "inspect" "d6fdd3c5c062693e85694e6c012712072e6978683b0d6f90c9272bd9764c6b6d", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d6fdd3c5c062693e85694e6c012712072e6978683b0d6f90c9272bd9764c6b6d", kill_on_drop: false }` [INFO] [stdout] d6fdd3c5c062693e85694e6c012712072e6978683b0d6f90c9272bd9764c6b6d [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/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:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 00407885d61cf216fdbdc02a6f057c7b195ac628c34a242a13b6ef7c95557876 [INFO] running `Command { std: "docker" "start" "-a" "00407885d61cf216fdbdc02a6f057c7b195ac628c34a242a13b6ef7c95557876", kill_on_drop: false }` [INFO] [stderr] Compiling embedded-io v0.4.0 [INFO] [stderr] Compiling chrono v0.4.41 [INFO] [stderr] Compiling ape-mbr v0.1.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/lib.rs:296:26 [INFO] [stdout] | [INFO] [stdout] 296 | pub fn get_partition(&mut self, id: PartitionId) -> Result, IO::Error> { [INFO] [stdout] | ^^^^^^^^^ ------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 296 | pub fn get_partition(&mut self, id: PartitionId) -> Result, IO::Error> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling ape-fatfs v0.1.0 [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:132:13 [INFO] [stdout] | [INFO] [stdout] 132 | / error!( [INFO] [stdout] 133 | | "invalid bytes_per_sector value in BPB: expected a power of two but got {}", [INFO] [stdout] 134 | | self.bytes_per_sector [INFO] [stdout] 135 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:139:13 [INFO] [stdout] | [INFO] [stdout] 139 | / error!( [INFO] [stdout] 140 | | "invalid bytes_per_sector value in BPB: expected value in range [512, 4096] but got {}", [INFO] [stdout] 141 | | self.bytes_per_sector [INFO] [stdout] 142 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:150:13 [INFO] [stdout] | [INFO] [stdout] 150 | / error!( [INFO] [stdout] 151 | | "invalid sectors_per_cluster value in BPB: expected a power of two but got {}", [INFO] [stdout] 152 | | self.sectors_per_cluster [INFO] [stdout] 153 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:157:13 [INFO] [stdout] | [INFO] [stdout] 157 | / error!( [INFO] [stdout] 158 | | "invalid sectors_per_cluster value in BPB: expected value in range [1, 128] but got {}", [INFO] [stdout] 159 | | self.sectors_per_cluster [INFO] [stdout] 160 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:173:13 [INFO] [stdout] | [INFO] [stdout] 173 | / ... warn!("fs compatibility: bytes_per_cluster value '{}' in BPB exceeds '{}', and thus may be incompatible with some implementations", [INFO] [stdout] 174 | | ... bytes_per_cluster, maximum_compatibility_bytes_per_cluster); [INFO] [stdout] | |_____________________________________________________________________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:182:13 [INFO] [stdout] | [INFO] [stdout] 182 | / error!( [INFO] [stdout] 183 | | "invalid reserved_sectors value in BPB: {}", [INFO] [stdout] 184 | | self.reserved_sectors [INFO] [stdout] 185 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:190:13 [INFO] [stdout] | [INFO] [stdout] 190 | / warn!( [INFO] [stdout] 191 | | "fs compatibility: reserved_sectors value '{}' in BPB is not '1', and thus is incompatible with some implementations", [INFO] [stdout] 192 | | self.reserved_sectors [INFO] [stdout] 193 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:196:13 [INFO] [stdout] | [INFO] [stdout] 196 | / error!( [INFO] [stdout] 197 | | "Invalid BPB: expected backup boot-sector to be in the reserved region (sector < {}) but got sector {}", [INFO] [stdout] 198 | | self.reserved_sectors, self.backup_boot_sector [INFO] [stdout] 199 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:203:13 [INFO] [stdout] | [INFO] [stdout] 203 | / error!( [INFO] [stdout] 204 | | "Invalid BPB: expected FSInfo sector to be in the reserved region (sector < {}) but got sector {}", [INFO] [stdout] 205 | | self.reserved_sectors, self.fs_info_sector [INFO] [stdout] 206 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:214:13 [INFO] [stdout] | [INFO] [stdout] 214 | error!("invalid fats value in BPB: {}", self.fats); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:219:13 [INFO] [stdout] | [INFO] [stdout] 219 | / warn!( [INFO] [stdout] 220 | | "fs compatibility: numbers of FATs '{}' in BPB is greater than '2', and thus is incompatible with some implementations", [INFO] [stdout] 221 | | self.fats [INFO] [stdout] 222 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:230:13 [INFO] [stdout] | [INFO] [stdout] 230 | / error!( [INFO] [stdout] 231 | | "Invalid root_entries value in FAT32 BPB: expected 0 but got {}", [INFO] [stdout] 232 | | self.root_entries [INFO] [stdout] 233 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:237:13 [INFO] [stdout] | [INFO] [stdout] 237 | / error!( [INFO] [stdout] 238 | | "Invalid root_entries value in FAT12/FAT16 BPB: expected non-zero value but got {}", [INFO] [stdout] 239 | | self.root_entries [INFO] [stdout] 240 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:244:13 [INFO] [stdout] | [INFO] [stdout] 244 | warn!("Root entries should fill sectors fully"); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:252:13 [INFO] [stdout] | [INFO] [stdout] 252 | / error!( [INFO] [stdout] 253 | | "Invalid total_sectors_16 value in FAT32 BPB: expected 0 but got {}", [INFO] [stdout] 254 | | self.total_sectors_16 [INFO] [stdout] 255 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:259:13 [INFO] [stdout] | [INFO] [stdout] 259 | error!("Invalid BPB (total_sectors_16 or total_sectors_32 should be non-zero)"); [INFO] [stdout] | ------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:265:13 [INFO] [stdout] | [INFO] [stdout] 265 | / error!( [INFO] [stdout] 266 | | "Invalid total_sectors value in BPB: expected value > {} but got {}", [INFO] [stdout] 267 | | first_data_sector, total_sectors [INFO] [stdout] 268 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:277:13 [INFO] [stdout] | [INFO] [stdout] 277 | / error!( [INFO] [stdout] 278 | | "Invalid sectors_per_fat_32 value in FAT32 BPB: expected non-zero value but got {}", [INFO] [stdout] 279 | | self.sectors_per_fat_32 [INFO] [stdout] 280 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:291:13 [INFO] [stdout] | [INFO] [stdout] 291 | error!("Invalid BPB: result of FAT32 determination from total number of clusters and sectors_per_fat_16 field differs"); [INFO] [stdout] | ----------------------------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:295:13 [INFO] [stdout] | [INFO] [stdout] 295 | error!("Invalid BPB: too many clusters {}", total_clusters); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:304:13 [INFO] [stdout] | [INFO] [stdout] 304 | / warn!( [INFO] [stdout] 305 | | "FAT is too small (allows allocation of {} clusters) compared to the total number of clusters ({})", [INFO] [stdout] 306 | | usable_fat_entries, total_clusters [INFO] [stdout] 307 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:314:13 [INFO] [stdout] | [INFO] [stdout] 314 | / error!( [INFO] [stdout] 315 | | "Unsupported filesystem version: expected 0 but got {}", [INFO] [stdout] 316 | | self.fs_version [INFO] [stdout] 317 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:468:13 [INFO] [stdout] | [INFO] [stdout] 468 | / error!( [INFO] [stdout] 469 | | "Invalid boot sector signature: expected [0x55, 0xAA] but got {:?}", [INFO] [stdout] 470 | | self.boot_sig [INFO] [stdout] 471 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:475:13 [INFO] [stdout] | [INFO] [stdout] 475 | / warn!( [INFO] [stdout] 476 | | "Unknown opcode {:x} in bootjmp boot sector field", [INFO] [stdout] 477 | | self.bootjmp[0] [INFO] [stdout] 478 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:618:9 [INFO] [stdout] | [INFO] [stdout] 618 | error!("Volume is too small"); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:639:9 [INFO] [stdout] | [INFO] [stdout] 639 | error!("Invalid FAT type"); [INFO] [stdout] | -------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:645:9 [INFO] [stdout] | [INFO] [stdout] 645 | error!("Too many clusters"); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:688:5 [INFO] [stdout] | [INFO] [stdout] 688 | error!("Cannot select FAT type - unfortunate storage size"); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/boot_sector.rs:790:9 [INFO] [stdout] | [INFO] [stdout] 790 | error!("Total number of clusters and FAT type does not match, please try a different volume size"); [INFO] [stdout] | -------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:142:25 [INFO] [stdout] | [INFO] [stdout] 142 | error!("Is a directory"); [INFO] [stdout] | ------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:144:25 [INFO] [stdout] | [INFO] [stdout] 144 | error!("Not a directory"); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:210:9 [INFO] [stdout] | [INFO] [stdout] 210 | trace!("Dir::open_dir {}", path); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:231:9 [INFO] [stdout] | [INFO] [stdout] 231 | trace!("Dir::open_file {}", path); [INFO] [stdout] | --------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:258:9 [INFO] [stdout] | [INFO] [stdout] 258 | trace!("Dir::create_file {}", path); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | trace!("Dir::create_dir {}", path); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:339:9 [INFO] [stdout] | [INFO] [stdout] 339 | trace!("Dir::is_empty"); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:367:9 [INFO] [stdout] | [INFO] [stdout] 367 | trace!("Dir::remove {}", path); [INFO] [stdout] | ------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:389:13 [INFO] [stdout] | [INFO] [stdout] 389 | trace!("removing dir entry {:?}", data); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:419:9 [INFO] [stdout] | [INFO] [stdout] 419 | trace!("Dir::rename {} {}", src_path, dst_path); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:442:9 [INFO] [stdout] | [INFO] [stdout] 442 | trace!("Dir::rename_internal {} {}", src_name, dst_name); [INFO] [stdout] | -------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:467:13 [INFO] [stdout] | [INFO] [stdout] 467 | trace!("removing LFN entry {:?}", data); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:566:9 [INFO] [stdout] | [INFO] [stdout] 566 | trace!("Dir::write_entry {}", name); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:648:9 [INFO] [stdout] | [INFO] [stdout] 648 | trace!("DirIter::read_dir_entry"); [INFO] [stdout] | --------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:661:17 [INFO] [stdout] | [INFO] [stdout] 661 | trace!("skip entry"); [INFO] [stdout] | -------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:680:21 [INFO] [stdout] | [INFO] [stdout] 680 | trace!("file entry {:?}", data.name()); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:693:21 [INFO] [stdout] | [INFO] [stdout] 693 | trace!("lfn entry"); [INFO] [stdout] | ------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:891:13 [INFO] [stdout] | [INFO] [stdout] 891 | warn!("unfinished LFN sequence {}", self.index); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:918:13 [INFO] [stdout] | [INFO] [stdout] 918 | warn!("currupted lfn entry! {:x}", data.order()); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:929:13 [INFO] [stdout] | [INFO] [stdout] 929 | / warn!( [INFO] [stdout] 930 | | "currupted lfn entry! {:x} {:x} {:x} {:x}", [INFO] [stdout] 931 | | data.order(), [INFO] [stdout] 932 | | self.index, [INFO] [stdout] 933 | | data.checksum(), [INFO] [stdout] 934 | | self.chksum [INFO] [stdout] 935 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir.rs:954:13 [INFO] [stdout] | [INFO] [stdout] 954 | / warn!( [INFO] [stdout] 955 | | "checksum mismatch {:x} {:x} {:?}", [INFO] [stdout] 956 | | chksum, self.chksum, short_name [INFO] [stdout] 957 | | ); [INFO] [stdout] | |_____________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir_entry.rs:372:9 [INFO] [stdout] | [INFO] [stdout] 372 | trace!("DirEntryData::serialize"); [INFO] [stdout] | --------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/dir_entry.rs:385:9 [INFO] [stdout] | [INFO] [stdout] 385 | trace!("DirEntryData::deserialize"); [INFO] [stdout] | ----------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:67:9 [INFO] [stdout] | [INFO] [stdout] 67 | trace!("File::truncate"); [INFO] [stdout] | ------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:241:13 [INFO] [stdout] | [INFO] [stdout] 241 | error!("flush failed {:?}", err); [INFO] [stdout] | -------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:265:9 [INFO] [stdout] | [INFO] [stdout] 265 | trace!("File::read"); [INFO] [stdout] | -------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:297:9 [INFO] [stdout] | [INFO] [stdout] 297 | trace!("read {} bytes in cluster {}", read_size, current_cluster); [INFO] [stdout] | ----------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:333:9 [INFO] [stdout] | [INFO] [stdout] 333 | trace!("File::write"); [INFO] [stdout] | --------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:365:17 [INFO] [stdout] | [INFO] [stdout] 365 | trace!("allocated cluster {}", new_cluster); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:378:9 [INFO] [stdout] | [INFO] [stdout] 378 | trace!("write {} bytes in cluster {}", write_size, current_cluster); [INFO] [stdout] | ------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:421:9 [INFO] [stdout] | [INFO] [stdout] 421 | trace!("File::seek"); [INFO] [stdout] | -------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:435:13 [INFO] [stdout] | [INFO] [stdout] 435 | error!("Invalid seek offset"); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:440:17 [INFO] [stdout] | [INFO] [stdout] 440 | warn!("Seek beyond the end of the file"); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/file.rs:444:9 [INFO] [stdout] | [INFO] [stdout] 444 | / trace!( [INFO] [stdout] 445 | | "file seek {} -> {} - entry {:?}", [INFO] [stdout] 446 | | self.offset, [INFO] [stdout] 447 | | new_offset, [INFO] [stdout] 448 | | self.entry [INFO] [stdout] 449 | | ); [INFO] [stdout] | |_________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:147:13 [INFO] [stdout] | [INFO] [stdout] 147 | error!("invalid lead_sig in FsInfo sector: {}", lead_sig); [INFO] [stdout] | --------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:154:13 [INFO] [stdout] | [INFO] [stdout] 154 | error!("invalid struc_sig in FsInfo sector: {}", struc_sig); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:165:17 [INFO] [stdout] | [INFO] [stdout] 165 | warn!("invalid next_free_cluster in FsInfo sector (values 0 and 1 are reserved)"); [INFO] [stdout] | --------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:175:13 [INFO] [stdout] | [INFO] [stdout] 175 | error!("invalid trail_sig in FsInfo sector: {}", trail_sig); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:202:17 [INFO] [stdout] | [INFO] [stdout] 202 | / warn!( [INFO] [stdout] 203 | | "invalid free_cluster_count ({}) in fs_info exceeds total cluster count ({})", [INFO] [stdout] 204 | | n, total_clusters [INFO] [stdout] 205 | | ); [INFO] [stdout] | |_________________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:211:17 [INFO] [stdout] | [INFO] [stdout] 211 | / warn!( [INFO] [stdout] 212 | | "invalid free_cluster_count ({}) in fs_info exceeds maximum cluster number ({})", [INFO] [stdout] 213 | | n, max_valid_cluster_number [INFO] [stdout] 214 | | ); [INFO] [stdout] | |_________________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:380:9 [INFO] [stdout] | [INFO] [stdout] 380 | trace!("FileSystem::new"); [INFO] [stdout] | ------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:415:9 [INFO] [stdout] | [INFO] [stdout] 415 | trace!("FileSystem::new end"); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:515:9 [INFO] [stdout] | [INFO] [stdout] 515 | trace!("alloc_cluster"); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:640:9 [INFO] [stdout] | [INFO] [stdout] 640 | trace!("root_dir"); [INFO] [stdout] | ------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:723:13 [INFO] [stdout] | [INFO] [stdout] 723 | error!("unmount failed {:?}", err); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:893:17 [INFO] [stdout] | [INFO] [stdout] 893 | error!("Seek beyond the end of the file"); [INFO] [stdout] | ----------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:900:13 [INFO] [stdout] | [INFO] [stdout] 900 | error!("Invalid seek offset"); [INFO] [stdout] | ----------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:1164:5 [INFO] [stdout] | [INFO] [stdout] 1164 | trace!("format_volume"); [INFO] [stdout] | ----------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:1175:13 [INFO] [stdout] | [INFO] [stdout] 1175 | error!("Volume has too many sectors: {}", total_sectors_64); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error 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[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/fs.rs:1261:5 [INFO] [stdout] | [INFO] [stdout] 1261 | trace!("format_volume end"); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/table.rs:97:5 [INFO] [stdout] | [INFO] [stdout] 97 | trace!("write FAT - cluster {} value {:?}", cluster, value); [INFO] [stdout] | ----------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/table.rs:171:5 [INFO] [stdout] | [INFO] [stdout] 171 | trace!("allocated cluster {}", new_cluster); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/table.rs:525:17 [INFO] [stdout] | [INFO] [stdout] 525 | / warn!( [INFO] [stdout] 526 | | "cluster number {} is a special value in FAT to indicate {}; it should never be seen as free", [INFO] [stdout] 527 | | cluster, tmp [INFO] [stdout] 528 | | ); [INFO] [stdout] | |_________________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0433]: failed to resolve: could not find `__log_module_path` in `log` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/log_macros.rs:54:52 [INFO] [stdout] | [INFO] [stdout] 54 | ($lvl:expr, $($arg:tt)+) => (log!(target: log::__log_module_path!(), $lvl, $($arg)+)) [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ could not find `__log_module_path` in `log` [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/ape-fatfs-0.1.0/src/table.rs:540:17 [INFO] [stdout] | [INFO] [stdout] 540 | ... warn!("cluster number {} is a special value in FAT to indicate {}; hiding potential FAT chain value {} and instead reporting as a bad sector", cluster, tmp, n); [INFO] [stdout] | --------------------------------------------------------------------------------------------------------------------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this error originates in the macro `log` which comes from the expansion of the macro `warn` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0433`. [INFO] [stdout] [INFO] [stderr] error: could not compile `ape-fatfs` (lib) due to 83 previous errors [INFO] running `Command { std: "docker" "inspect" "00407885d61cf216fdbdc02a6f057c7b195ac628c34a242a13b6ef7c95557876", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "00407885d61cf216fdbdc02a6f057c7b195ac628c34a242a13b6ef7c95557876", kill_on_drop: false }` [INFO] [stdout] 00407885d61cf216fdbdc02a6f057c7b195ac628c34a242a13b6ef7c95557876