[INFO] fetching crate trillium-macros 0.0.6...
[INFO] testing trillium-macros-0.0.6 against beta-2025-10-28 for beta-1.92-2
[INFO] extracting crate trillium-macros 0.0.6 into /workspace/builds/worker-5-tc2/source
[INFO] started tweaking crates.io crate trillium-macros 0.0.6
[INFO] finished tweaking crates.io crate trillium-macros 0.0.6
[INFO] tweaked toml for crates.io crate trillium-macros 0.0.6 written to /workspace/builds/worker-5-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate trillium-macros 0.0.6 on toolchain beta-2025-10-28
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-10-28" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-10-28" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 10 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-10-28" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-10-28" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 7ba45d72883b0880fb51dbbd774cf600e5e99347822849b1efc30effda17cb33
[INFO] running `Command { std: "docker" "start" "-a" "7ba45d72883b0880fb51dbbd774cf600e5e99347822849b1efc30effda17cb33", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "7ba45d72883b0880fb51dbbd774cf600e5e99347822849b1efc30effda17cb33", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "7ba45d72883b0880fb51dbbd774cf600e5e99347822849b1efc30effda17cb33", kill_on_drop: false }`
[INFO] [stdout] 7ba45d72883b0880fb51dbbd774cf600e5e99347822849b1efc30effda17cb33
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-10-28" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] fd3a72345fa5eda9988a50ec7fe349fb91898e60bb48fddac2f70a5c0c2dced1
[INFO] running `Command { std: "docker" "start" "-a" "fd3a72345fa5eda9988a50ec7fe349fb91898e60bb48fddac2f70a5c0c2dced1", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v2.0.108
[INFO] [stderr]    Compiling trillium-macros v0.0.6 (/opt/rustwide/workdir)
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.88s
[INFO] running `Command { std: "docker" "inspect" "fd3a72345fa5eda9988a50ec7fe349fb91898e60bb48fddac2f70a5c0c2dced1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "fd3a72345fa5eda9988a50ec7fe349fb91898e60bb48fddac2f70a5c0c2dced1", kill_on_drop: false }`
[INFO] [stdout] fd3a72345fa5eda9988a50ec7fe349fb91898e60bb48fddac2f70a5c0c2dced1
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-10-28" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 6d0db6d4c06c73fc71648b8c24497f3fa3f9826b6b6c8f63e7497422eb304b77
[INFO] running `Command { std: "docker" "start" "-a" "6d0db6d4c06c73fc71648b8c24497f3fa3f9826b6b6c8f63e7497422eb304b77", kill_on_drop: false }`
[INFO] [stderr]    Compiling quote v1.0.41
[INFO] [stderr]    Compiling futures-core v0.3.31
[INFO] [stderr]    Compiling fastrand v2.3.0
[INFO] [stderr]    Compiling parking v2.2.1
[INFO] [stderr]    Compiling syn v2.0.108
[INFO] [stderr]    Compiling futures-lite v2.6.1
[INFO] [stderr]    Compiling trillium-macros v0.0.6 (/opt/rustwide/workdir)
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium_testing`
[INFO] [stdout]  --> tests/derive.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 | use trillium_testing::prelude::*;
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_testing`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_testing`, use `cargo add trillium_testing` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]  --> tests/derive.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use trillium::{Handler, Info, Status::Ok};
[INFO] [stdout]   |     ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium`
[INFO] [stdout]  --> tests/derive.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use trillium::{Handler, Info, Status::Ok};
[INFO] [stdout]   |     ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:16:7
[INFO] [stdout]    |
[INFO] [stdout] 16 |     #[trillium::async_trait]
[INFO] [stdout]    |       ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:36:14
[INFO] [stdout]    |
[INFO] [stdout] 36 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:53:14
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:63:14
[INFO] [stdout]    |
[INFO] [stdout] 63 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:73:14
[INFO] [stdout]    |
[INFO] [stdout] 73 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:87:14
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:104:14
[INFO] [stdout]     |
[INFO] [stdout] 104 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:108:14
[INFO] [stdout]     |
[INFO] [stdout] 108 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium_http`
[INFO] [stdout]  --> tests/transport.rs:4:5
[INFO] [stdout]   |
[INFO] [stdout] 4 | use trillium_http::Synthetic;
[INFO] [stdout]   |     ^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_http`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_http`, use `cargo add trillium_http` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:116:14
[INFO] [stdout]     |
[INFO] [stdout] 116 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `trillium_server_common`
[INFO] [stdout]  --> tests/transport.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 | use trillium_server_common::{AsyncRead, AsyncWrite, Transport};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:123:14
[INFO] [stdout]     |
[INFO] [stdout] 123 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:129:14
[INFO] [stdout]     |
[INFO] [stdout] 129 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:138:14
[INFO] [stdout]     |
[INFO] [stdout] 138 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:153:14
[INFO] [stdout]     |
[INFO] [stdout] 153 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:172:14
[INFO] [stdout]     |
[INFO] [stdout] 172 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]    --> tests/transport.rs:72:48
[INFO] [stdout]     |
[INFO] [stdout]  72 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 112 |     define_transport_with_except!(OuterTransport);
[INFO] [stdout]     |     --------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]   --> tests/derive.rs:46:9
[INFO] [stdout]    |
[INFO] [stdout] 46 |         assert_ok!(get("/").run_async(&handler).await, "run", "before-send" => "before-send");
[INFO] [stdout]    |         ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout]    = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]   --> tests/derive.rs:58:5
[INFO] [stdout]    |
[INFO] [stdout] 58 |     assert_ok!(get("/").on(&handler), "hi");
[INFO] [stdout]    |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout]    = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]   --> tests/derive.rs:68:5
[INFO] [stdout]    |
[INFO] [stdout] 68 |     assert_ok!(get("/").on(&handler), "hi");
[INFO] [stdout]    |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout]    = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]   --> tests/derive.rs:82:5
[INFO] [stdout]    |
[INFO] [stdout] 82 |     assert_ok!(get("/").on(&handler), "hi");
[INFO] [stdout]    |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout]    = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]   --> tests/derive.rs:99:5
[INFO] [stdout]    |
[INFO] [stdout] 99 |     assert_ok!(get("/").on(&handler), "hi");
[INFO] [stdout]    |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]    |
[INFO] [stdout]   --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]    |
[INFO] [stdout]    = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]    --> tests/derive.rs:114:5
[INFO] [stdout]     |
[INFO] [stdout] 114 |     assert_ok!(get("/").on(&handler));
[INFO] [stdout]     |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: cannot find macro `assert_ok` in this scope
[INFO] [stdout]    --> tests/derive.rs:136:5
[INFO] [stdout]     |
[INFO] [stdout] 136 |     assert_ok!(get("/").on(&handler));
[INFO] [stdout]     |     ^^^^^^^^^ help: a macro with a similar name exists: `assert_eq`
[INFO] [stdout]     |
[INFO] [stdout]    --> /rustc/3b4dd9bf1410f8da6329baa36ce5e37673cbbd1f/library/core/src/macros/mod.rs:42:1
[INFO] [stdout]     |
[INFO] [stdout]     = note: similarly named macro `assert_eq` defined here
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]    --> tests/transport.rs:72:48
[INFO] [stdout]     |
[INFO] [stdout]  72 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 127 |     define_transport_with_except!(OuterTransport, except = set_linger);
[INFO] [stdout]     |     ------------------------------------------------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]    --> tests/transport.rs:72:48
[INFO] [stdout]     |
[INFO] [stdout]  72 |         #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 142 |     define_transport_with_except!(OuterTransport, except = [set_nodelay, peer_addr]);
[INFO] [stdout]     |     -------------------------------------------------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:36:14
[INFO] [stdout]    |
[INFO] [stdout] 36 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout]    --> tests/transport.rs:72:48
[INFO] [stdout]     |
[INFO] [stdout]  72 |           #[derive(Debug, AsyncRead, AsyncWrite, Transport)]
[INFO] [stdout]     |                                                  ^^^^^^^^^ use of unresolved module or unlinked crate `trillium_server_common`
[INFO] [stdout] ...
[INFO] [stdout] 157 | /     define_transport_with_except!(
[INFO] [stdout] 158 | |         OuterTransport,
[INFO] [stdout] 159 | |         except = [set_linger, set_nodelay, set_ip_ttl, peer_addr],
[INFO] [stdout] 160 | |     );
[INFO] [stdout]     | |_____- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium_server_common`, use `cargo add trillium_server_common` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Transport` which comes from the expansion of the macro `define_transport_with_except` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `trillium-macros` (test "transport") due to 6 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:53:14
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:63:14
[INFO] [stdout]    |
[INFO] [stdout] 63 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:73:14
[INFO] [stdout]    |
[INFO] [stdout] 73 |     #[derive(Handler, Clone)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]   --> tests/derive.rs:87:14
[INFO] [stdout]    |
[INFO] [stdout] 87 |     #[derive(Handler)]
[INFO] [stdout]    |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:104:14
[INFO] [stdout]     |
[INFO] [stdout] 104 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:108:14
[INFO] [stdout]     |
[INFO] [stdout] 108 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:116:14
[INFO] [stdout]     |
[INFO] [stdout] 116 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:123:14
[INFO] [stdout]     |
[INFO] [stdout] 123 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:129:14
[INFO] [stdout]     |
[INFO] [stdout] 129 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:138:14
[INFO] [stdout]     |
[INFO] [stdout] 138 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:153:14
[INFO] [stdout]     |
[INFO] [stdout] 153 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:166:16
[INFO] [stdout]     |
[INFO] [stdout] 166 |     assert_eq!(trillium::Handler::name(&handler), "custom name (handler)");
[INFO] [stdout]     |                ^^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: failed to resolve: use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]    --> tests/derive.rs:172:14
[INFO] [stdout]     |
[INFO] [stdout] 172 |     #[derive(Handler)]
[INFO] [stdout]     |              ^^^^^^^ use of unresolved module or unlinked crate `trillium`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `trillium`, use `cargo add trillium` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `Handler` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]   --> tests/derive.rs:18:35
[INFO] [stdout]    |
[INFO] [stdout] 18 |         async fn run(&self, conn: Conn) -> Conn {
[INFO] [stdout]    |                                   ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]   --> tests/derive.rs:18:44
[INFO] [stdout]    |
[INFO] [stdout] 18 |         async fn run(&self, conn: Conn) -> Conn {
[INFO] [stdout]    |                                            ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]   --> tests/derive.rs:27:43
[INFO] [stdout]    |
[INFO] [stdout] 27 |         async fn before_send(&self, conn: Conn) -> Conn {
[INFO] [stdout]    |                                           ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]   --> tests/derive.rs:27:52
[INFO] [stdout]    |
[INFO] [stdout] 27 |         async fn before_send(&self, conn: Conn) -> Conn {
[INFO] [stdout]    |                                                    ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `block_on` in this scope
[INFO] [stdout]   --> tests/derive.rs:39:5
[INFO] [stdout]    |
[INFO] [stdout] 39 |     block_on(async {
[INFO] [stdout]    |     ^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout] help: consider importing one of these functions
[INFO] [stdout]    |
[INFO] [stdout]  3 + use futures_lite::future::block_on;
[INFO] [stdout]    |
[INFO] [stdout]  3 + use futures_lite::stream::block_on;
[INFO] [stdout]    |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]    --> tests/derive.rs:180:35
[INFO] [stdout]     |
[INFO] [stdout] 180 |         async fn run(&self, conn: Conn) -> Conn {
[INFO] [stdout]     |                                   ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]    --> tests/derive.rs:180:44
[INFO] [stdout]     |
[INFO] [stdout] 180 |         async fn run(&self, conn: Conn) -> Conn {
[INFO] [stdout]     |                                            ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]    --> tests/derive.rs:187:43
[INFO] [stdout]     |
[INFO] [stdout] 187 |         async fn before_send(&self, conn: Conn) -> Conn {
[INFO] [stdout]     |                                           ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0412]: cannot find type `Conn` in this scope
[INFO] [stdout]    --> tests/derive.rs:187:52
[INFO] [stdout]     |
[INFO] [stdout] 187 |         async fn before_send(&self, conn: Conn) -> Conn {
[INFO] [stdout]     |                                                    ^^^^ not found in this scope
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0412, E0425, E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0412`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `trillium-macros` (test "derive") due to 47 previous errors
[INFO] running `Command { std: "docker" "inspect" "6d0db6d4c06c73fc71648b8c24497f3fa3f9826b6b6c8f63e7497422eb304b77", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6d0db6d4c06c73fc71648b8c24497f3fa3f9826b6b6c8f63e7497422eb304b77", kill_on_drop: false }`
[INFO] [stdout] 6d0db6d4c06c73fc71648b8c24497f3fa3f9826b6b6c8f63e7497422eb304b77
