[INFO] fetching crate noble-contracts 2.0.0... [INFO] checking noble-contracts-2.0.0 against try#b20a093d9fb1ffaa04ae9852cb034864a992bafd for pr-85073 [INFO] extracting crate noble-contracts 2.0.0 into /workspace/builds/worker-5/source [INFO] validating manifest of crates.io crate noble-contracts 2.0.0 on toolchain b20a093d9fb1ffaa04ae9852cb034864a992bafd [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+b20a093d9fb1ffaa04ae9852cb034864a992bafd" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate noble-contracts 2.0.0 [INFO] finished tweaking crates.io crate noble-contracts 2.0.0 [INFO] tweaked toml for crates.io crate noble-contracts 2.0.0 written to /workspace/builds/worker-5/source/Cargo.toml [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+b20a093d9fb1ffaa04ae9852cb034864a992bafd" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+b20a093d9fb1ffaa04ae9852cb034864a992bafd" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/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:20528e8c29e4536546f0102ce88568b16ea7538393a33fcca951030f7af10457" "/opt/rustwide/cargo-home/bin/cargo" "+b20a093d9fb1ffaa04ae9852cb034864a992bafd" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 430bb9d909bcce81d49bca44b4994e8c1f4a9671a096a03bb158cd40cce23aad [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" "430bb9d909bcce81d49bca44b4994e8c1f4a9671a096a03bb158cd40cce23aad", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "430bb9d909bcce81d49bca44b4994e8c1f4a9671a096a03bb158cd40cce23aad", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "430bb9d909bcce81d49bca44b4994e8c1f4a9671a096a03bb158cd40cce23aad", kill_on_drop: false }` [INFO] [stdout] 430bb9d909bcce81d49bca44b4994e8c1f4a9671a096a03bb158cd40cce23aad [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5/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" "ghcr.io/rust-lang/crates-build-env/linux@sha256:20528e8c29e4536546f0102ce88568b16ea7538393a33fcca951030f7af10457" "/opt/rustwide/cargo-home/bin/cargo" "+b20a093d9fb1ffaa04ae9852cb034864a992bafd" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 5f0a2805a0f6396eaef71441263132036257f160b808e5dc820de5b65a76bce7 [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" "5f0a2805a0f6396eaef71441263132036257f160b808e5dc820de5b65a76bce7", kill_on_drop: false }` [INFO] [stderr] Checking leb128 v0.2.4 [INFO] [stderr] Checking safe-mix v1.0.1 [INFO] [stderr] Checking ansi_term v0.11.0 [INFO] [stderr] Checking difference v2.0.0 [INFO] [stderr] Compiling hex-literal v0.3.1 [INFO] [stderr] Checking twasm-utils v0.16.0 [INFO] [stderr] Compiling noble-contracts-proc-macro v0.1.0 [INFO] [stderr] Checking simba v0.4.0 [INFO] [stderr] Checking serde v1.0.126 [INFO] [stderr] Checking futures-util v0.3.15 [INFO] [stderr] Checking ref-cast v1.0.6 [INFO] [stderr] Checking thiserror v1.0.25 [INFO] [stderr] Checking dyn-clonable v0.9.0 [INFO] [stderr] Checking zeroize v1.3.0 [INFO] [stderr] Checking nalgebra v0.19.0 [INFO] [stderr] Checking wast v35.0.2 [INFO] [stderr] Checking curve25519-dalek v2.1.2 [INFO] [stderr] Checking merlin v2.0.1 [INFO] [stderr] Checking curve25519-dalek v3.1.0 [INFO] [stderr] Checking tiny-bip39 v0.8.0 [INFO] [stderr] Checking secrecy v0.7.0 [INFO] [stderr] Checking pretty_assertions v0.6.1 [INFO] [stderr] Checking futures-executor v0.3.15 [INFO] [stderr] Compiling toml v0.5.8 [INFO] [stderr] Checking futures v0.3.15 [INFO] [stderr] Checking tetsy-impl-serde v0.3.1 [INFO] [stderr] Checking impl-serde v0.3.1 [INFO] [stderr] Checking serde_json v1.0.64 [INFO] [stderr] Checking tracing-serde v0.1.2 [INFO] [stderr] Checking schnorrkel v0.9.1 [INFO] [stderr] Checking ed25519-dalek v1.0.1 [INFO] [stderr] Checking wasm-timer v0.2.5 [INFO] [stderr] Checking tetcore-bip39 v0.4.2 [INFO] [stderr] Checking wat v1.0.37 [INFO] [stderr] Compiling proc-macro-crate v0.1.5 [INFO] [stderr] Compiling fabric-support-procedural-tools v2.0.1 [INFO] [stderr] Checking tracing-subscriber v0.2.18 [INFO] [stderr] Compiling tetsy-scale-codec-derive v2.0.1 [INFO] [stderr] Compiling tp-runtime-interface-proc-macro v2.0.2 [INFO] [stderr] Compiling tp-api-proc-macro v2.0.2 [INFO] [stderr] Compiling fabric-support-procedural v2.0.1 [INFO] [stderr] Checking nalgebra v0.25.4 [INFO] [stderr] Checking tetsy-scale-codec v2.0.1 [INFO] [stderr] Checking tetsy-impl-codec v0.5.0 [INFO] [stderr] Checking tetcore-storage v2.0.2 [INFO] [stderr] Checking tetcore-wasm-interface v2.0.2 [INFO] [stderr] Checking tetcore-tracing v2.0.2 [INFO] [stderr] Checking arithmetic v2.0.2 [INFO] [stderr] Checking tetsy-primitive-types v0.9.0 [INFO] [stderr] Checking externalities v0.8.2 [INFO] [stderr] Checking tetsy-util-mem v0.9.0 [INFO] [stderr] Checking tp-runtime-interface v2.0.2 [INFO] [stderr] Checking tetsy-memory-db v0.26.0 [INFO] [stderr] Checking tet-core v2.0.2 [INFO] [stderr] Checking statrs v0.13.0 [INFO] [stderr] Checking tp-trie v2.0.2 [INFO] [stderr] Checking tp-keystore v0.8.1 [INFO] [stderr] Checking tp-inherents v2.0.2 [INFO] [stderr] Checking fabric-metadata v12.0.0 [INFO] [stderr] Checking tp-state-machine v0.8.2 [INFO] [stderr] Checking tet-io v2.0.2 [INFO] [stderr] Checking tet-application-crypto v2.0.2 [INFO] [stderr] Checking tp-sandbox v0.8.2 [INFO] [stderr] Checking tp-runtime v2.0.2 [INFO] [stderr] Checking linregress v0.4.1 [INFO] [stderr] Checking tp-version v2.0.2 [INFO] [stderr] Checking fabric-support v2.0.0 [INFO] [stderr] Checking noble-contracts-primitives v2.0.0 [INFO] [stderr] Checking tp-api v2.0.2 [INFO] [stderr] Checking tp-timestamp v2.0.2 [INFO] [stderr] Checking fabric-system v2.0.0 [INFO] [stderr] Checking fabric-benchmarking v2.0.0 [INFO] [stderr] Checking noble-randomness-collective-flip v2.0.0 [INFO] [stderr] Checking noble-contracts v2.0.0 (/opt/rustwide/workdir) [INFO] [stderr] Checking noble-timestamp v2.0.0 [INFO] [stderr] Checking noble-balances v2.0.1 [INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 562 | / prepare_test!(param_number_valid, [INFO] [stdout] 563 | | r#" [INFO] [stdout] 564 | | (module [INFO] [stdout] 565 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 570 | | Ok(_) [INFO] [stdout] 571 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:560:7 [INFO] [stdout] | [INFO] [stdout] 560 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 573 | / prepare_test!(param_number_invalid, [INFO] [stdout] 574 | | r#" [INFO] [stdout] 575 | | (module [INFO] [stdout] 576 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 582 | | Err("Use of a function type with too many parameters.") [INFO] [stdout] 583 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:560:7 [INFO] [stdout] | [INFO] [stdout] 560 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 589 | / prepare_test!(global_number_valid, [INFO] [stdout] 590 | | r#" [INFO] [stdout] 591 | | (module [INFO] [stdout] 592 | | (global i64 (i64.const 0)) [INFO] [stdout] ... | [INFO] [stdout] 599 | | Ok(_) [INFO] [stdout] 600 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:587:7 [INFO] [stdout] | [INFO] [stdout] 587 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 602 | / prepare_test!(global_number_too_high, [INFO] [stdout] 603 | | r#" [INFO] [stdout] 604 | | (module [INFO] [stdout] 605 | | (global i64 (i64.const 0)) [INFO] [stdout] ... | [INFO] [stdout] 613 | | Err("module declares too many globals") [INFO] [stdout] 614 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:587:7 [INFO] [stdout] | [INFO] [stdout] 587 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 620 | / prepare_test!(memory_with_one_page, [INFO] [stdout] 621 | | r#" [INFO] [stdout] 622 | | (module [INFO] [stdout] 623 | | (import "env" "memory" (memory 1 1)) [INFO] [stdout] ... | [INFO] [stdout] 629 | | Ok(_) [INFO] [stdout] 630 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 632 | / prepare_test!(internal_memory_declaration, [INFO] [stdout] 633 | | r#" [INFO] [stdout] 634 | | (module [INFO] [stdout] 635 | | (memory 1 1) [INFO] [stdout] ... | [INFO] [stdout] 641 | | Err("module declares internal memory") [INFO] [stdout] 642 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 644 | / prepare_test!(no_memory_import, [INFO] [stdout] 645 | | r#" [INFO] [stdout] 646 | | (module [INFO] [stdout] 647 | | ;; no memory imported [INFO] [stdout] ... | [INFO] [stdout] 652 | | Ok(_) [INFO] [stdout] 653 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 655 | / prepare_test!(initial_exceeds_maximum, [INFO] [stdout] 656 | | r#" [INFO] [stdout] 657 | | (module [INFO] [stdout] 658 | | (import "env" "memory" (memory 16 1)) [INFO] [stdout] ... | [INFO] [stdout] 664 | | Err("Module is not valid") [INFO] [stdout] 665 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 667 | / prepare_test!(no_maximum, [INFO] [stdout] 668 | | r#" [INFO] [stdout] 669 | | (module [INFO] [stdout] 670 | | (import "env" "memory" (memory 1)) [INFO] [stdout] ... | [INFO] [stdout] 676 | | Err("Maximum number of pages should be always declared.") [INFO] [stdout] 677 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 679 | / prepare_test!(requested_maximum_valid, [INFO] [stdout] 680 | | r#" [INFO] [stdout] 681 | | (module [INFO] [stdout] 682 | | (import "env" "memory" (memory 1 16)) [INFO] [stdout] ... | [INFO] [stdout] 688 | | Ok(_) [INFO] [stdout] 689 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 691 | / prepare_test!(requested_maximum_exceeds_configured_maximum, [INFO] [stdout] 692 | | r#" [INFO] [stdout] 693 | | (module [INFO] [stdout] 694 | | (import "env" "memory" (memory 1 17)) [INFO] [stdout] ... | [INFO] [stdout] 700 | | Err("Maximum number of pages should not exceed the configured maximum.") [INFO] [stdout] 701 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 703 | / prepare_test!(field_name_not_memory, [INFO] [stdout] 704 | | r#" [INFO] [stdout] 705 | | (module [INFO] [stdout] 706 | | (import "env" "forgetit" (memory 1 1)) [INFO] [stdout] ... | [INFO] [stdout] 712 | | Err("Memory import must have the field name 'memory'") [INFO] [stdout] 713 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 715 | / prepare_test!(multiple_memory_imports, [INFO] [stdout] 716 | | r#" [INFO] [stdout] 717 | | (module [INFO] [stdout] 718 | | (import "env" "memory" (memory 1 1)) [INFO] [stdout] ... | [INFO] [stdout] 725 | | Err("Module is not valid") [INFO] [stdout] 726 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 728 | / prepare_test!(table_import, [INFO] [stdout] 729 | | r#" [INFO] [stdout] 730 | | (module [INFO] [stdout] 731 | | (import "seal0" "table" (table 1 anyfunc)) [INFO] [stdout] ... | [INFO] [stdout] 737 | | Err("Cannot import tables") [INFO] [stdout] 738 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 740 | / prepare_test!(global_import, [INFO] [stdout] 741 | | r#" [INFO] [stdout] 742 | | (module [INFO] [stdout] 743 | | (global $g (import "seal0" "global") i32) [INFO] [stdout] ... | [INFO] [stdout] 748 | | Err("Cannot import globals") [INFO] [stdout] 749 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:618:7 [INFO] [stdout] | [INFO] [stdout] 618 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 755 | / prepare_test!(no_tables, [INFO] [stdout] 756 | | r#" [INFO] [stdout] 757 | | (module [INFO] [stdout] 758 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 762 | | Ok(_) [INFO] [stdout] 763 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:753:7 [INFO] [stdout] | [INFO] [stdout] 753 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 765 | / prepare_test!(table_valid_size, [INFO] [stdout] 766 | | r#" [INFO] [stdout] 767 | | (module [INFO] [stdout] 768 | | (table 3 funcref) [INFO] [stdout] ... | [INFO] [stdout] 774 | | Ok(_) [INFO] [stdout] 775 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:753:7 [INFO] [stdout] | [INFO] [stdout] 753 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 777 | / prepare_test!(table_too_big, [INFO] [stdout] 778 | | r#" [INFO] [stdout] 779 | | (module [INFO] [stdout] 780 | | (table 4 funcref) [INFO] [stdout] ... | [INFO] [stdout] 785 | | Err("table exceeds maximum size allowed") [INFO] [stdout] 786 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:753:7 [INFO] [stdout] | [INFO] [stdout] 753 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 788 | / prepare_test!(br_table_valid_size, [INFO] [stdout] 789 | | r#" [INFO] [stdout] 790 | | (module [INFO] [stdout] 791 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 799 | | Ok(_) [INFO] [stdout] 800 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:753:7 [INFO] [stdout] | [INFO] [stdout] 753 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 802 | / prepare_test!(br_table_too_big, [INFO] [stdout] 803 | | r#" [INFO] [stdout] 804 | | (module [INFO] [stdout] 805 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 812 | | Err("BrTable's immediate value is too big.") [INFO] [stdout] 813 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:753:7 [INFO] [stdout] | [INFO] [stdout] 753 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 819 | / prepare_test!(can_import_legit_function, [INFO] [stdout] 820 | | r#" [INFO] [stdout] 821 | | (module [INFO] [stdout] 822 | | (import "seal0" "nop" (func (param i64))) [INFO] [stdout] ... | [INFO] [stdout] 828 | | Ok(_) [INFO] [stdout] 829 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 833 | / prepare_test!(can_not_import_gas_function, [INFO] [stdout] 834 | | r#" [INFO] [stdout] 835 | | (module [INFO] [stdout] 836 | | (import "seal0" "gas" (func (param i32))) [INFO] [stdout] ... | [INFO] [stdout] 842 | | Err("module imports a non-existent function") [INFO] [stdout] 843 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 846 | / prepare_test!(memory_not_in_seal0, [INFO] [stdout] 847 | | r#" [INFO] [stdout] 848 | | (module [INFO] [stdout] 849 | | (import "seal0" "memory" (memory 1 1)) [INFO] [stdout] ... | [INFO] [stdout] 855 | | Err("Invalid module for imported memory") [INFO] [stdout] 856 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 859 | / prepare_test!(memory_not_in_arbitrary_module, [INFO] [stdout] 860 | | r#" [INFO] [stdout] 861 | | (module [INFO] [stdout] 862 | | (import "any_module" "memory" (memory 1 1)) [INFO] [stdout] ... | [INFO] [stdout] 868 | | Err("Invalid module for imported memory") [INFO] [stdout] 869 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 872 | / prepare_test!(function_not_in_env, [INFO] [stdout] 873 | | r#" [INFO] [stdout] 874 | | (module [INFO] [stdout] 875 | | (import "env" "nop" (func (param i64))) [INFO] [stdout] ... | [INFO] [stdout] 881 | | Err("Invalid module for imported function") [INFO] [stdout] 882 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 885 | / prepare_test!(function_not_arbitrary_module, [INFO] [stdout] 886 | | r#" [INFO] [stdout] 887 | | (module [INFO] [stdout] 888 | | (import "any_module" "nop" (func (param i64))) [INFO] [stdout] ... | [INFO] [stdout] 894 | | Err("Invalid module for imported function") [INFO] [stdout] 895 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 898 | / prepare_test!(wrong_signature, [INFO] [stdout] 899 | | r#" [INFO] [stdout] 900 | | (module [INFO] [stdout] 901 | | (import "seal0" "gas" (func (param i64))) [INFO] [stdout] ... | [INFO] [stdout] 907 | | Err("module imports a non-existent function") [INFO] [stdout] 908 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 910 | / prepare_test!(unknown_func_name, [INFO] [stdout] 911 | | r#" [INFO] [stdout] 912 | | (module [INFO] [stdout] 913 | | (import "seal0" "unknown_func" (func)) [INFO] [stdout] ... | [INFO] [stdout] 919 | | Err("module imports a non-existent function") [INFO] [stdout] 920 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 922 | / prepare_test!(seal_println_debug_disabled, [INFO] [stdout] 923 | | r#" [INFO] [stdout] 924 | | (module [INFO] [stdout] 925 | | (import "seal0" "seal_println" (func $seal_println (param i32 i32))) [INFO] [stdout] ... | [INFO] [stdout] 931 | | Err("module imports `seal_println` but debug features disabled") [INFO] [stdout] 932 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:949:4 [INFO] [stdout] | [INFO] [stdout] 949 | assert_matches!(r, Ok(_)); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:817:7 [INFO] [stdout] | [INFO] [stdout] 817 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 956 | / prepare_test!(it_works, [INFO] [stdout] 957 | | r#" [INFO] [stdout] 958 | | (module [INFO] [stdout] 959 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 963 | | Ok(_) [INFO] [stdout] 964 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 966 | / prepare_test!(omit_deploy, [INFO] [stdout] 967 | | r#" [INFO] [stdout] 968 | | (module [INFO] [stdout] 969 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 972 | | Err("deploy function isn't exported") [INFO] [stdout] 973 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 975 | / prepare_test!(omit_call, [INFO] [stdout] 976 | | r#" [INFO] [stdout] 977 | | (module [INFO] [stdout] 978 | | (func (export "deploy")) [INFO] [stdout] ... | [INFO] [stdout] 981 | | Err("call function isn't exported") [INFO] [stdout] 982 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 985 | / prepare_test!(try_sneak_export_as_entrypoint, [INFO] [stdout] 986 | | r#" [INFO] [stdout] 987 | | (module [INFO] [stdout] 988 | | (import "seal0" "panic" (func)) [INFO] [stdout] ... | [INFO] [stdout] 995 | | Err("entry point points to an imported function") [INFO] [stdout] 996 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 999 | / prepare_test!(try_sneak_export_as_global, [INFO] [stdout] 1000 | | r#" [INFO] [stdout] 1001 | | (module [INFO] [stdout] 1002 | | (func (export "deploy")) [INFO] [stdout] ... | [INFO] [stdout] 1006 | | Err("expected a function") [INFO] [stdout] 1007 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1009 | / prepare_test!(wrong_signature, [INFO] [stdout] 1010 | | r#" [INFO] [stdout] 1011 | | (module [INFO] [stdout] 1012 | | (func (export "deploy")) [INFO] [stdout] ... | [INFO] [stdout] 1016 | | Err("entry point has wrong signature") [INFO] [stdout] 1017 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1019 | / prepare_test!(unknown_exports, [INFO] [stdout] 1020 | | r#" [INFO] [stdout] 1021 | | (module [INFO] [stdout] 1022 | | (func (export "call")) [INFO] [stdout] ... | [INFO] [stdout] 1027 | | Err("unknown export: expecting only deploy and call functions") [INFO] [stdout] 1028 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1030 | / prepare_test!(global_float, [INFO] [stdout] 1031 | | r#" [INFO] [stdout] 1032 | | (module [INFO] [stdout] 1033 | | (global $x f32 (f32.const 0)) [INFO] [stdout] ... | [INFO] [stdout] 1038 | | Err("use of floating point type in globals is forbidden") [INFO] [stdout] 1039 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1041 | / prepare_test!(local_float, [INFO] [stdout] 1042 | | r#" [INFO] [stdout] 1043 | | (module [INFO] [stdout] 1044 | | (func $foo (local f32)) [INFO] [stdout] ... | [INFO] [stdout] 1049 | | Err("use of floating point type in locals is forbidden") [INFO] [stdout] 1050 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1052 | / prepare_test!(param_float, [INFO] [stdout] 1053 | | r#" [INFO] [stdout] 1054 | | (module [INFO] [stdout] 1055 | | (func $foo (param f32)) [INFO] [stdout] ... | [INFO] [stdout] 1060 | | Err("use of floating point type in function types is forbidden") [INFO] [stdout] 1061 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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[E0659]: `assert_matches` is ambiguous (glob import vs any other name from outer scope during import/macro resolution) [INFO] [stdout] --> src/wasm/prepare.rs:538:5 [INFO] [stdout] | [INFO] [stdout] 538 | assert_matches!(r, $($expected)*); [INFO] [stdout] | ^^^^^^^^^^^^^^ ambiguous name [INFO] [stdout] ... [INFO] [stdout] 1063 | / prepare_test!(result_float, [INFO] [stdout] 1064 | | r#" [INFO] [stdout] 1065 | | (module [INFO] [stdout] 1066 | | (func $foo (result f32) (f32.const 0)) [INFO] [stdout] ... | [INFO] [stdout] 1071 | | Err("use of floating point type in function types is forbidden") [INFO] [stdout] 1072 | | ); [INFO] [stdout] | |__________- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `assert_matches` could refer to a macro from prelude [INFO] [stdout] note: `assert_matches` could also refer to the macro imported here [INFO] [stdout] --> src/wasm/prepare.rs:954:7 [INFO] [stdout] | [INFO] [stdout] 954 | use super::*; [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = help: consider adding an explicit import of `assert_matches` to disambiguate [INFO] [stdout] = help: or use `self::assert_matches` to refer to this macro unambiguously [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: aborting due to 41 previous errors [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0659`. [INFO] [stdout] [INFO] [stderr] error: could not compile `noble-contracts` [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `Command { std: "docker" "inspect" "5f0a2805a0f6396eaef71441263132036257f160b808e5dc820de5b65a76bce7", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5f0a2805a0f6396eaef71441263132036257f160b808e5dc820de5b65a76bce7", kill_on_drop: false }` [INFO] [stdout] 5f0a2805a0f6396eaef71441263132036257f160b808e5dc820de5b65a76bce7