[INFO] cloning repository https://github.com/DCasFer/RustSimpleScheduler [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/DCasFer/RustSimpleScheduler" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FDCasFer%2FRustSimpleScheduler", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FDCasFer%2FRustSimpleScheduler'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 25cda9d5d9601a56296589861556e7c173fbff04 [INFO] checking DCasFer/RustSimpleScheduler against try#8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8 for pr-82565 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FDCasFer%2FRustSimpleScheduler" "/workspace/builds/worker-0/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-0/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/DCasFer/RustSimpleScheduler on toolchain 8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8 [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] removed /workspace/builds/worker-0/source/.cargo/config [INFO] started tweaking git repo https://github.com/DCasFer/RustSimpleScheduler [INFO] finished tweaking git repo https://github.com/DCasFer/RustSimpleScheduler [INFO] tweaked toml for git repo https://github.com/DCasFer/RustSimpleScheduler written to /workspace/builds/worker-0/source/Cargo.toml [INFO] crate git repo https://github.com/DCasFer/RustSimpleScheduler already has a lockfile, it will not be regenerated [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8" "fetch" "--locked" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/workspace/builds/worker-0/source/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/workspace/builds/worker-0/source/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/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" "rustops/crates-build-env@sha256:f2f6bcd4b43ebee4e173f653a26493129bdb64017c85f916b780ca7fbdbaa79d" "/opt/rustwide/cargo-home/bin/cargo" "+8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 746c7b342e32268dc6311432228c35a6e58ae8dfec5703201b457a07bb38a7d9 [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `Command { std: "docker" "start" "-a" "746c7b342e32268dc6311432228c35a6e58ae8dfec5703201b457a07bb38a7d9", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "746c7b342e32268dc6311432228c35a6e58ae8dfec5703201b457a07bb38a7d9", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "746c7b342e32268dc6311432228c35a6e58ae8dfec5703201b457a07bb38a7d9", kill_on_drop: false }` [INFO] [stdout] 746c7b342e32268dc6311432228c35a6e58ae8dfec5703201b457a07bb38a7d9 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0/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" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "rustops/crates-build-env@sha256:f2f6bcd4b43ebee4e173f653a26493129bdb64017c85f916b780ca7fbdbaa79d" "/opt/rustwide/cargo-home/bin/cargo" "+8e3afc79c11f48cb3acd1be5b3b7de98fe3f93a8" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 7a9bad62d7c5e7ed5a9d5e7479247135ed1458476f8d8e5ac77a8dbee13f80c6 [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] running `Command { std: "docker" "start" "-a" "7a9bad62d7c5e7ed5a9d5e7479247135ed1458476f8d8e5ac77a8dbee13f80c6", kill_on_drop: false }` [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package embrs v0.1.0 (/opt/rustwide/workdir/embrs), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `cpu:cortex-m4f` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc:stm32f407` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `:` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `[` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] warning: invalid character `]` in feature `soc_family:stm32f4[01]` in package scheduler v0.1.0 (/opt/rustwide/workdir/scheduler), characters must be Unicode XID characters, `+`, or `.` (numbers, `+`, `-`, `_`, `.`, or most letters) [INFO] [stderr] This was previously accepted but is being phased out; it will become a hard error in a future release. [INFO] [stderr] For more information, see issue #8813 , and please leave a comment if this will be a problem for your project. [INFO] [stderr] Compiling emb1 v0.1.0 (/opt/rustwide/workdir) [INFO] [stderr] Checking bitflags v0.7.0 [INFO] [stderr] Checking rlibc v1.0.0 [INFO] [stderr] Checking embrs v0.1.0 (/opt/rustwide/workdir/embrs) [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 126 | ex_impl!(u32); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 127 | ex_impl!(u16); [INFO] [stdout] | -------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: expected type, found `"=&r"` [INFO] [stdout] --> embrs/src/arm_m/reg.rs:78:24 [INFO] [stdout] | [INFO] [stdout] 78 | : "=&r"(tmp) [INFO] [stdout] | - ^^^^^ expected type [INFO] [stdout] | | [INFO] [stdout] | tried to parse a type due to this type ascription [INFO] [stdout] ... [INFO] [stdout] 128 | ex_impl!(u8); [INFO] [stdout] | ------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#![feature(type_ascription)]` lets you annotate an expression with a type: `: ` [INFO] [stdout] = note: see issue #23416 for more information [INFO] [stdout] = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:14:9 [INFO] [stdout] | [INFO] [stdout] 14 | asm!("msr PRIMASK, $0" [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | _________help: replace with: `llvm_asm!` [INFO] [stdout] | | [INFO] [stdout] 15 | | :: "r"(val) [INFO] [stdout] 16 | | :: "volatile") [INFO] [stdout] | |___________________________^ [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:14:9 [INFO] [stdout] | [INFO] [stdout] 14 | asm!("msr PRIMASK, $0" [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | _________help: replace with: `llvm_asm!` [INFO] [stdout] | | [INFO] [stdout] 15 | | :: "r"(val) [INFO] [stdout] 16 | | :: "volatile") [INFO] [stdout] | |___________________________^ [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:24:9 [INFO] [stdout] | [INFO] [stdout] 24 | asm!("isb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:32:9 [INFO] [stdout] | [INFO] [stdout] 32 | asm!("dsb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:40:9 [INFO] [stdout] | [INFO] [stdout] 40 | asm!("dmb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:47:9 [INFO] [stdout] | [INFO] [stdout] 47 | asm!("wfi" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:24:9 [INFO] [stdout] | [INFO] [stdout] 24 | asm!("isb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:32:9 [INFO] [stdout] | [INFO] [stdout] 32 | asm!("dsb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:40:9 [INFO] [stdout] | [INFO] [stdout] 40 | asm!("dmb" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: the legacy LLVM-style asm! syntax is no longer supported [INFO] [stdout] --> embrs/src/arm_m/mod.rs:47:9 [INFO] [stdout] | [INFO] [stdout] 47 | asm!("wfi" :::: "volatile") [INFO] [stdout] | ----^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: replace with: `llvm_asm!` [INFO] [stdout] | [INFO] [stdout] = note: consider migrating to the new asm! syntax specified in RFC 2873 [INFO] [stdout] = note: alternatively, switch to llvm_asm! to keep your code working as it is [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused macro definition [INFO] [stdout] --> embrs/src/arm_m/reg.rs:89:1 [INFO] [stdout] | [INFO] [stdout] 89 | / macro_rules! ex_suffix { [INFO] [stdout] 90 | | (u32) => { "" }; [INFO] [stdout] 91 | | (i32) => { "" }; [INFO] [stdout] 92 | | (u16) => { "h" }; [INFO] [stdout] ... | [INFO] [stdout] 95 | | (i8) => { "b" }; [INFO] [stdout] 96 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_macros)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/dma.rs:91:1 [INFO] [stdout] | [INFO] [stdout] 91 | / bitflags! { [INFO] [stdout] 92 | | /// The set of interrupt bit flags that can appear for a given DMA stream. [INFO] [stdout] 93 | | /// These are used to indicate stream status (in the Interrupt Status [INFO] [stdout] 94 | | /// Registers) and to change it (in the Interrupt Flag Clear Registers). [INFO] [stdout] ... | [INFO] [stdout] 101 | | } [INFO] [stdout] 102 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(deprecated)]` on by default [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/dma.rs:91:1 [INFO] [stdout] | [INFO] [stdout] 91 | / bitflags! { [INFO] [stdout] 92 | | /// The set of interrupt bit flags that can appear for a given DMA stream. [INFO] [stdout] 93 | | /// These are used to indicate stream status (in the Interrupt Status [INFO] [stdout] 94 | | /// Registers) and to change it (in the Interrupt Flag Clear Registers). [INFO] [stdout] ... | [INFO] [stdout] 101 | | } [INFO] [stdout] 102 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/gpio.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | / bitflags! { [INFO] [stdout] 82 | | /// Names a group of pins on a single GPIO port. The STM32F4 GPIO is [INFO] [stdout] 83 | | /// designed so that most operations can be applied to any subset of pins [INFO] [stdout] 84 | | /// for the same cost as a single pin, so we expose that oddity here. [INFO] [stdout] ... | [INFO] [stdout] 104 | | } [INFO] [stdout] 105 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/gpio.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | / bitflags! { [INFO] [stdout] 82 | | /// Names a group of pins on a single GPIO port. The STM32F4 GPIO is [INFO] [stdout] 83 | | /// designed so that most operations can be applied to any subset of pins [INFO] [stdout] 84 | | /// for the same cost as a single pin, so we expose that oddity here. [INFO] [stdout] ... | [INFO] [stdout] 104 | | } [INFO] [stdout] 105 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variant `PendSV_IRQn` should have an upper camel case name [INFO] [stdout] --> embrs/src/stm32f4/irq.rs:237:5 [INFO] [stdout] | [INFO] [stdout] 237 | PendSV_IRQn = -2, //David [INFO] [stdout] | ^^^^^^^^^^^ help: convert the identifier to upper camel case: `PendSvIrqn` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(non_camel_case_types)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused macro definition [INFO] [stdout] --> embrs/src/arm_m/reg.rs:89:1 [INFO] [stdout] | [INFO] [stdout] 89 | / macro_rules! ex_suffix { [INFO] [stdout] 90 | | (u32) => { "" }; [INFO] [stdout] 91 | | (i32) => { "" }; [INFO] [stdout] 92 | | (u16) => { "h" }; [INFO] [stdout] ... | [INFO] [stdout] 95 | | (i8) => { "b" }; [INFO] [stdout] 96 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_macros)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/dma.rs:91:1 [INFO] [stdout] | [INFO] [stdout] 91 | / bitflags! { [INFO] [stdout] 92 | | /// The set of interrupt bit flags that can appear for a given DMA stream. [INFO] [stdout] 93 | | /// These are used to indicate stream status (in the Interrupt Status [INFO] [stdout] 94 | | /// Registers) and to change it (in the Interrupt Flag Clear Registers). [INFO] [stdout] ... | [INFO] [stdout] 101 | | } [INFO] [stdout] 102 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(deprecated)]` on by default [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/dma.rs:91:1 [INFO] [stdout] | [INFO] [stdout] 91 | / bitflags! { [INFO] [stdout] 92 | | /// The set of interrupt bit flags that can appear for a given DMA stream. [INFO] [stdout] 93 | | /// These are used to indicate stream status (in the Interrupt Status [INFO] [stdout] 94 | | /// Registers) and to change it (in the Interrupt Flag Clear Registers). [INFO] [stdout] ... | [INFO] [stdout] 101 | | } [INFO] [stdout] 102 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/gpio.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | / bitflags! { [INFO] [stdout] 82 | | /// Names a group of pins on a single GPIO port. The STM32F4 GPIO is [INFO] [stdout] 83 | | /// designed so that most operations can be applied to any subset of pins [INFO] [stdout] 84 | | /// for the same cost as a single pin, so we expose that oddity here. [INFO] [stdout] ... | [INFO] [stdout] 104 | | } [INFO] [stdout] 105 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead [INFO] [stdout] --> embrs/src/stm32f4/gpio.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | / bitflags! { [INFO] [stdout] 82 | | /// Names a group of pins on a single GPIO port. The STM32F4 GPIO is [INFO] [stdout] 83 | | /// designed so that most operations can be applied to any subset of pins [INFO] [stdout] 84 | | /// for the same cost as a single pin, so we expose that oddity here. [INFO] [stdout] ... | [INFO] [stdout] 104 | | } [INFO] [stdout] 105 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variant `PendSV_IRQn` should have an upper camel case name [INFO] [stdout] --> embrs/src/stm32f4/irq.rs:237:5 [INFO] [stdout] | [INFO] [stdout] 237 | PendSV_IRQn = -2, //David [INFO] [stdout] | ^^^^^^^^^^^ help: convert the identifier to upper camel case: `PendSvIrqn` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(non_camel_case_types)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0522]: definition of an unknown language item: `panic_fmt` [INFO] [stdout] --> embrs/src/lang.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | #[lang = "panic_fmt"] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ definition of unknown language item `panic_fmt` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0522]: definition of an unknown language item: `panic_fmt` [INFO] [stdout] --> embrs/src/lang.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | #[lang = "panic_fmt"] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ definition of unknown language item `panic_fmt` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: aborting due to 15 previous errors; 6 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0522`. [INFO] [stdout] [INFO] [stderr] error: could not compile `embrs` [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] error: aborting due to 15 previous errors; 6 warnings emitted [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0522`. [INFO] [stdout] [INFO] [stderr] error: build failed [INFO] running `Command { std: "docker" "inspect" "7a9bad62d7c5e7ed5a9d5e7479247135ed1458476f8d8e5ac77a8dbee13f80c6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7a9bad62d7c5e7ed5a9d5e7479247135ed1458476f8d8e5ac77a8dbee13f80c6", kill_on_drop: false }` [INFO] [stdout] 7a9bad62d7c5e7ed5a9d5e7479247135ed1458476f8d8e5ac77a8dbee13f80c6