[INFO] cloning repository https://github.com/planetoryd/mirai_issue
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/planetoryd/mirai_issue" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fplanetoryd%2Fmirai_issue", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fplanetoryd%2Fmirai_issue'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] 53f4884353344e6dac42e9a0bfe68023ec5cd7db
[INFO] checking planetoryd/mirai_issue against try#fa4dd1f19bfeb3fd235dc7f1406c42404436bef5 for pr-145108-2
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fplanetoryd%2Fmirai_issue" "/workspace/builds/worker-1-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc2/source'...
[INFO] [stderr] done.
[INFO] started tweaking git repo https://github.com/planetoryd/mirai_issue
[INFO] finished tweaking git repo https://github.com/planetoryd/mirai_issue
[INFO] tweaked toml for git repo https://github.com/planetoryd/mirai_issue written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/planetoryd/mirai_issue on toolchain fa4dd1f19bfeb3fd235dc7f1406c42404436bef5
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/planetoryd/mirai_issue already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]     Blocking waiting for file lock on package cache
[ERROR] error running command: no output for 300 seconds
[INFO] checking planetoryd/mirai_issue against try#fa4dd1f19bfeb3fd235dc7f1406c42404436bef5 for pr-145108-2
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fplanetoryd%2Fmirai_issue" "/workspace/builds/worker-1-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc2/source'...
[INFO] [stderr] done.
[INFO] started tweaking git repo https://github.com/planetoryd/mirai_issue
[INFO] finished tweaking git repo https://github.com/planetoryd/mirai_issue
[INFO] tweaked toml for git repo https://github.com/planetoryd/mirai_issue written to /workspace/builds/worker-1-tc2/source/Cargo.toml
[INFO] validating manifest of git repo https://github.com/planetoryd/mirai_issue on toolchain fa4dd1f19bfeb3fd235dc7f1406c42404436bef5
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate git repo https://github.com/planetoryd/mirai_issue already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded async-global-executor v2.3.1
[INFO] [stderr]   Downloaded amplify_syn v2.0.1
[INFO] [stderr]   Downloaded contracts v0.6.3
[INFO] [stderr]   Downloaded value-bag v1.4.1
[INFO] [stderr]   Downloaded amplify_derive v3.0.1
[INFO] [stderr]   Downloaded syn v2.0.35
[INFO] [stderr]   Downloaded rustix v0.37.23
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:61361fe0aef631f17e9d025a70c5a647956f8c671dd02950a60ad3f5cc5526d7" "/opt/rustwide/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 7fd82446224039fed0f31a91a2115d3463475947f007d95106ea0b18fd886cc9
[INFO] running `Command { std: "docker" "start" "-a" "7fd82446224039fed0f31a91a2115d3463475947f007d95106ea0b18fd886cc9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "7fd82446224039fed0f31a91a2115d3463475947f007d95106ea0b18fd886cc9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7fd82446224039fed0f31a91a2115d3463475947f007d95106ea0b18fd886cc9", kill_on_drop: false }`
[INFO] [stdout] 7fd82446224039fed0f31a91a2115d3463475947f007d95106ea0b18fd886cc9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:61361fe0aef631f17e9d025a70c5a647956f8c671dd02950a60ad3f5cc5526d7" "/opt/rustwide/cargo-home/bin/cargo" "+fa4dd1f19bfeb3fd235dc7f1406c42404436bef5" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] df9c77ea72e0052d4b93115a94ea74327577859c0d0a137168d7ec5a1e7af54a
[INFO] running `Command { std: "docker" "start" "-a" "df9c77ea72e0052d4b93115a94ea74327577859c0d0a137168d7ec5a1e7af54a", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.148
[INFO] [stderr]    Compiling proc-macro2 v1.0.67
[INFO] [stderr]    Compiling futures-core v0.3.28
[INFO] [stderr]     Checking value-bag v1.4.1
[INFO] [stderr]     Checking parking v2.1.0
[INFO] [stderr]     Checking memchr v2.6.3
[INFO] [stderr]     Checking futures-io v0.3.28
[INFO] [stderr]     Checking async-lock v2.8.0
[INFO] [stderr]    Compiling polling v2.8.0
[INFO] [stderr]    Compiling rustix v0.37.23
[INFO] [stderr]    Compiling async-io v1.13.0
[INFO] [stderr]     Checking linux-raw-sys v0.3.8
[INFO] [stderr]     Checking async-task v4.4.0
[INFO] [stderr]     Checking concurrent-queue v2.2.0
[INFO] [stderr]     Checking atomic-waker v1.1.1
[INFO] [stderr]     Checking mirai-annotations v1.12.0
[INFO] [stderr]     Checking log v0.4.20
[INFO] [stderr]     Checking async-channel v1.9.0
[INFO] [stderr]     Checking futures-lite v1.13.0
[INFO] [stderr]     Checking kv-log-macro v1.0.7
[INFO] [stderr]    Compiling quote v1.0.33
[INFO] [stderr]     Checking io-lifetimes v1.0.11
[INFO] [stderr]     Checking socket2 v0.4.9
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]     Checking async-executor v1.5.1
[INFO] [stderr]     Checking blocking v1.3.1
[INFO] [stderr]     Checking async-global-executor v2.3.1
[INFO] [stderr]    Compiling amplify_syn v2.0.1
[INFO] [stderr]    Compiling async-attributes v1.1.2
[INFO] [stderr]    Compiling contracts v0.6.3
[INFO] [stderr]    Compiling amplify_derive v3.0.1
[INFO] [stderr]     Checking async-std v1.12.0
[INFO] [stderr]     Checking mirai_issue v0.1.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]  --> src/lib.rs:7:5
[INFO] [stdout]   |
[INFO] [stdout] 7 |     verify!(false); // works
[INFO] [stdout]   |     ^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 |     verify!(false);
[INFO] [stdout]    |     ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:18:9
[INFO] [stdout]    |
[INFO] [stdout] 18 |         verify!(false) // works
[INFO] [stdout]    |         ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:26:9
[INFO] [stdout]    |
[INFO] [stdout] 26 |         verify!(false)
[INFO] [stdout]    |         ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:32:5
[INFO] [stdout]    |
[INFO] [stdout] 32 |     verify!(false);
[INFO] [stdout]    |     ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]  --> src/test.rs:9:5
[INFO] [stdout]   |
[INFO] [stdout] 9 |     verify!(false);
[INFO] [stdout]   |     ^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/test.rs:15:5
[INFO] [stdout]    |
[INFO] [stdout] 15 |     verify!(false);
[INFO] [stdout]    |     ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/test.rs:23:5
[INFO] [stdout]    |
[INFO] [stdout] 23 |     verify!(false)
[INFO] [stdout]    |     ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]  --> src/lib.rs:7:5
[INFO] [stdout]   |
[INFO] [stdout] 7 |     verify!(false); // works
[INFO] [stdout]   |     ^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]   = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]   = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]   = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:11:5
[INFO] [stdout]    |
[INFO] [stdout] 11 |     verify!(false);
[INFO] [stdout]    |     ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:18:9
[INFO] [stdout]    |
[INFO] [stdout] 18 |         verify!(false) // works
[INFO] [stdout]    |         ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `mirai`
[INFO] [stdout]   --> src/lib.rs:26:9
[INFO] [stdout]    |
[INFO] [stdout] 26 |         verify!(false)
[INFO] [stdout]    |         ^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `verify` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `verify` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `verify` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 10.43s
[INFO] running `Command { std: "docker" "inspect" "df9c77ea72e0052d4b93115a94ea74327577859c0d0a137168d7ec5a1e7af54a", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "df9c77ea72e0052d4b93115a94ea74327577859c0d0a137168d7ec5a1e7af54a", kill_on_drop: false }`
[INFO] [stdout] df9c77ea72e0052d4b93115a94ea74327577859c0d0a137168d7ec5a1e7af54a
