[INFO] fetching crate rustyms 0.9.0-alpha.3... [INFO] checking rustyms-0.9.0-alpha.3 against try#50b21af28e291c419ae81eebcb7705fb4200dc90 for pr-135167 [INFO] extracting crate rustyms 0.9.0-alpha.3 into /workspace/builds/worker-0-tc2/source [INFO] validating manifest of crates.io crate rustyms 0.9.0-alpha.3 on toolchain 50b21af28e291c419ae81eebcb7705fb4200dc90 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+50b21af28e291c419ae81eebcb7705fb4200dc90" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate rustyms 0.9.0-alpha.3 [INFO] finished tweaking crates.io crate rustyms 0.9.0-alpha.3 [INFO] tweaked toml for crates.io crate rustyms 0.9.0-alpha.3 written to /workspace/builds/worker-0-tc2/source/Cargo.toml [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+50b21af28e291c419ae81eebcb7705fb4200dc90" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Locking 120 packages to latest compatible versions [INFO] [stderr] Adding itertools v0.13.0 (available: v0.14.0) [INFO] [stderr] Adding mzdata v0.36.0 (available: v0.41.0) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+50b21af28e291c419ae81eebcb7705fb4200dc90" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+50b21af28e291c419ae81eebcb7705fb4200dc90" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] ceff108f4261397bcba28ddc3a3685769718319fb8abb684ca1255bdbd2329ad [INFO] running `Command { std: "docker" "start" "-a" "ceff108f4261397bcba28ddc3a3685769718319fb8abb684ca1255bdbd2329ad", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "ceff108f4261397bcba28ddc3a3685769718319fb8abb684ca1255bdbd2329ad", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ceff108f4261397bcba28ddc3a3685769718319fb8abb684ca1255bdbd2329ad", kill_on_drop: false }` [INFO] [stdout] ceff108f4261397bcba28ddc3a3685769718319fb8abb684ca1255bdbd2329ad [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+50b21af28e291c419ae81eebcb7705fb4200dc90" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] e9b1c879dd8761dac09ed33d84b4ab8e45940babb7f0e4a82ac9a212dca4e949 [INFO] running `Command { std: "docker" "start" "-a" "e9b1c879dd8761dac09ed33d84b4ab8e45940babb7f0e4a82ac9a212dca4e949", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.93 [INFO] [stderr] Compiling unicode-ident v1.0.14 [INFO] [stderr] Compiling autocfg v1.4.0 [INFO] [stderr] Compiling serde v1.0.217 [INFO] [stderr] Compiling libc v0.2.169 [INFO] [stderr] Compiling typenum v1.17.0 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling shlex v1.3.0 [INFO] [stderr] Checking memchr v2.7.4 [INFO] [stderr] Compiling crossbeam-utils v0.8.21 [INFO] [stderr] Compiling serde_json v1.0.135 [INFO] [stderr] Compiling vcpkg v0.2.15 [INFO] [stderr] Compiling pkg-config v0.3.31 [INFO] [stderr] Compiling libm v0.2.11 [INFO] [stderr] Checking byteorder v1.5.0 [INFO] [stderr] Compiling cc v1.2.9 [INFO] [stderr] Checking regex-syntax v0.8.5 [INFO] [stderr] Compiling rayon-core v1.12.1 [INFO] [stderr] Checking adler2 v2.0.0 [INFO] [stderr] Compiling thiserror v2.0.11 [INFO] [stderr] Checking miniz_oxide v0.8.2 [INFO] [stderr] Checking crc32fast v1.4.2 [INFO] [stderr] Compiling generic-array v0.14.7 [INFO] [stderr] Compiling ryu v1.0.18 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling matrixmultiply v0.3.9 [INFO] [stderr] Checking aho-corasick v1.1.3 [INFO] [stderr] Compiling iai-callgrind-runner v0.14.0 [INFO] [stderr] Checking vsimd v0.8.0 [INFO] [stderr] Compiling quote v1.0.38 [INFO] [stderr] Compiling cmake v0.1.52 [INFO] [stderr] Checking crossbeam-epoch v0.9.18 [INFO] [stderr] Checking iana-time-zone v0.1.61 [INFO] [stderr] Compiling syn v2.0.96 [INFO] [stderr] Checking cpufeatures v0.2.16 [INFO] [stderr] Checking equivalent v1.0.1 [INFO] [stderr] Checking rawpointer v0.2.1 [INFO] [stderr] Checking itoa v1.0.14 [INFO] [stderr] Checking either v1.13.0 [INFO] [stderr] Checking outref v0.5.1 [INFO] [stderr] Checking crossbeam-deque v0.8.6 [INFO] [stderr] Checking hashbrown v0.15.2 [INFO] [stderr] Checking base64-simd v0.8.0 [INFO] [stderr] Checking special v0.10.3 [INFO] [stderr] Compiling proc-macro-error-attr2 v2.0.0 [INFO] [stderr] Checking getrandom v0.2.15 [INFO] [stderr] Checking bitflags v2.7.0 [INFO] [stderr] Checking lazy_static v1.5.0 [INFO] [stderr] Checking random v0.13.2 [INFO] [stderr] Checking identity-hash v0.1.0 [INFO] [stderr] Checking bytemuck v1.21.0 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Checking num-integer v0.1.46 [INFO] [stderr] Checking num-complex v0.4.6 [INFO] [stderr] Checking chrono v0.4.39 [INFO] [stderr] Checking mzpeaks v0.23.0 [INFO] [stderr] Compiling iai-callgrind v0.14.0 [INFO] [stderr] Checking md5 v0.7.0 [INFO] [stderr] Checking base16ct v0.2.0 [INFO] [stderr] Checking log v0.4.22 [INFO] [stderr] Checking regex-automata v0.4.9 [INFO] [stderr] Checking probability v0.20.3 [INFO] [stderr] Checking ndarray v0.16.1 [INFO] [stderr] Checking itertools v0.13.0 [INFO] [stderr] Checking similar v2.6.0 [INFO] [stderr] Compiling libz-sys v1.1.21 [INFO] [stderr] Checking block-buffer v0.10.4 [INFO] [stderr] Checking crypto-common v0.1.6 [INFO] [stderr] Checking rayon v1.10.0 [INFO] [stderr] Checking digest v0.10.7 [INFO] [stderr] Checking sha1 v0.10.6 [INFO] [stderr] Checking regex v1.11.1 [INFO] [stderr] Compiling proc-macro-error2 v2.0.1 [INFO] [stderr] Compiling serde_derive v1.0.217 [INFO] [stderr] Compiling zerocopy-derive v0.7.35 [INFO] [stderr] Compiling derive_more-impl v1.0.0 [INFO] [stderr] Compiling thiserror-impl v2.0.11 [INFO] [stderr] Checking zerocopy v0.7.35 [INFO] [stderr] Compiling derive_more v1.0.0 [INFO] [stderr] Checking ppv-lite86 v0.2.20 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Checking flate2 v1.0.35 [INFO] [stderr] Checking indexmap v2.7.0 [INFO] [stderr] Checking bincode v1.3.3 [INFO] [stderr] Checking quick-xml v0.30.0 [INFO] [stderr] Checking num-rational v0.4.2 [INFO] [stderr] Checking ordered-float v4.6.0 [INFO] [stderr] Checking thin-vec v0.2.13 [INFO] [stderr] Checking uom v0.36.0 [INFO] [stderr] Checking mzdata v0.36.0 [INFO] [stderr] Compiling iai-callgrind-macros v0.5.0 [INFO] [stderr] Checking rustyms v0.9.0-alpha.3 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: requested on the command line with `-W unexpected-cfgs` [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: requested on the command line with `-W unexpected-cfgs` [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:22:5 [INFO] [stdout] | [INFO] [stdout] 22 | / quantity! { [INFO] [stdout] 23 | | /// Mass in dalton [INFO] [stdout] 24 | | quantity: Mass; "mass"; [INFO] [stdout] 25 | | /// Mass [INFO] [stdout] ... | [INFO] [stdout] 33 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:41:5 [INFO] [stdout] | [INFO] [stdout] 41 | / quantity! { [INFO] [stdout] 42 | | /// Charge in electrons [INFO] [stdout] 43 | | quantity: Charge; "charge"; [INFO] [stdout] 44 | | /// Charge [INFO] [stdout] ... | [INFO] [stdout] 49 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:57:5 [INFO] [stdout] | [INFO] [stdout] 57 | / quantity! { [INFO] [stdout] 58 | | /// Time (s) [INFO] [stdout] 59 | | quantity: Time; "time"; [INFO] [stdout] 60 | | /// Time [INFO] [stdout] ... | [INFO] [stdout] 70 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:78:5 [INFO] [stdout] | [INFO] [stdout] 78 | / quantity! { [INFO] [stdout] 79 | | /// Mass over charge (da/e) [INFO] [stdout] 80 | | quantity: MassOverCharge; "mass_over_charge"; [INFO] [stdout] 81 | | /// Mass over charge (da/e) [INFO] [stdout] ... | [INFO] [stdout] 86 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:94:5 [INFO] [stdout] | [INFO] [stdout] 94 | / quantity! { [INFO] [stdout] 95 | | /// Unit less quantity for general calculations [INFO] [stdout] 96 | | quantity: Ratio; "ratio"; [INFO] [stdout] 97 | | /// Unit less quantity for general calculations [INFO] [stdout] ... | [INFO] [stdout] 108 | | } [INFO] [stdout] | |_____^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `quantity` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `quantity` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `quantity` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `si` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `f32` [INFO] [stdout] --> src/system.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | / system! { [INFO] [stdout] 112 | | /// Quantities [INFO] [stdout] 113 | | #[doc(hidden)] [INFO] [stdout] 114 | | quantities: Q { [INFO] [stdout] ... | [INFO] [stdout] 128 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `align`, `default`, `identification`, `imgt`, `isotopes`, `mzdata`, `ndarray`, `probability`, `rand`, and `rayon` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `system` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `system` may come from an old version of the `uom` crate, try updating your dependency with `cargo update -p uom` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `system` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `len` is never used [INFO] [stdout] --> src/identification/common_parser.rs:165:12 [INFO] [stdout] | [INFO] [stdout] 164 | impl<'a> Location<'a> { [INFO] [stdout] | --------------------- method in this implementation [INFO] [stdout] 165 | pub fn len(&self) -> usize { [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `rustyms` (lib); 103 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/50b21af28e291c419ae81eebcb7705fb4200dc90/bin/rustc --crate-name rustyms --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata -C embed-bitcode=no -C debuginfo=2 --warn=unexpected_cfgs --check-cfg 'cfg(github_action)' --cfg 'feature="align"' --cfg 'feature="default"' --cfg 'feature="identification"' --cfg 'feature="imgt"' --cfg 'feature="isotopes"' --cfg 'feature="mzdata"' --cfg 'feature="ndarray"' --cfg 'feature="probability"' --cfg 'feature="rand"' --cfg 'feature="rayon"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("align", "default", "identification", "imgt", "isotopes", "mzdata", "ndarray", "probability", "rand", "rayon"))' -C metadata=cdd33a9089fd05db -C extra-filename=-9483b871b9d57778 --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern bincode=/opt/rustwide/target/debug/deps/libbincode-58c8a0ad40f2afa6.rmeta --extern flate2=/opt/rustwide/target/debug/deps/libflate2-5d1202efdaa84403.rmeta --extern itertools=/opt/rustwide/target/debug/deps/libitertools-12de846c3d608b5f.rmeta --extern mzdata=/opt/rustwide/target/debug/deps/libmzdata-b0b644c4f03bd280.rmeta --extern ndarray=/opt/rustwide/target/debug/deps/libndarray-d5d5f474ffcbbbfb.rmeta --extern ordered_float=/opt/rustwide/target/debug/deps/libordered_float-dd208dd1da94a6df.rmeta --extern probability=/opt/rustwide/target/debug/deps/libprobability-5bd7368db6272c61.rmeta --extern rand=/opt/rustwide/target/debug/deps/librand-963cdb9f0b169f91.rmeta --extern rayon=/opt/rustwide/target/debug/deps/librayon-90b008b0c85e7d71.rmeta --extern regex=/opt/rustwide/target/debug/deps/libregex-9c3941406f686ce8.rmeta --extern serde=/opt/rustwide/target/debug/deps/libserde-d2af0ff240df6917.rmeta --extern similar=/opt/rustwide/target/debug/deps/libsimilar-2c14cf8476fff1b3.rmeta --extern thin_vec=/opt/rustwide/target/debug/deps/libthin_vec-2ebe85adda660885.rmeta --extern uom=/opt/rustwide/target/debug/deps/libuom-fedf07091c731dd1.rmeta --cap-lints=forbid -L native=/opt/rustwide/target/debug/build/libz-sys-bfc66e0b3bfdd7d9/out/lib -L native=/opt/rustwide/target/debug/build/libz-sys-bfc66e0b3bfdd7d9/out/lib64` (signal: 9, SIGKILL: kill) [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] warning: method `len` is never used [INFO] [stdout] --> src/identification/common_parser.rs:165:12 [INFO] [stdout] | [INFO] [stdout] 164 | impl<'a> Location<'a> { [INFO] [stdout] | --------------------- method in this implementation [INFO] [stdout] 165 | pub fn len(&self) -> usize { [INFO] [stdout] | ^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: function `iupac_masses` is never used [INFO] [stdout] --> src/glycan/monosaccharide.rs:375:8 [INFO] [stdout] | [INFO] [stdout] 375 | fn iupac_masses() { [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: missing documentation for a macro [INFO] [stdout] --> src/peptide/tests/mod.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | macro_rules! parse_test { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:2:57 [INFO] [stdout] | [INFO] [stdout] 2 | #![warn(clippy::all, clippy::pedantic, clippy::nursery, missing_docs)] [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: missing documentation for a macro [INFO] [stdout] --> src/peptide/tests/mod.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | macro_rules! parse_sloppy_test { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "e9b1c879dd8761dac09ed33d84b4ab8e45940babb7f0e4a82ac9a212dca4e949", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "e9b1c879dd8761dac09ed33d84b4ab8e45940babb7f0e4a82ac9a212dca4e949", kill_on_drop: false }` [INFO] [stdout] e9b1c879dd8761dac09ed33d84b4ab8e45940babb7f0e4a82ac9a212dca4e949