[INFO] fetching crate bigint 4.4.3...
[INFO] testing bigint-4.4.3 against master#1871252fc8bb672d40787e67404e6eaae7059369 for pr-125151
[INFO] extracting crate bigint 4.4.3 into /workspace/builds/worker-4-tc1/source
[INFO] validating manifest of crates.io crate bigint 4.4.3 on toolchain 1871252fc8bb672d40787e67404e6eaae7059369
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate bigint 4.4.3
[INFO] removed 0 missing examples
[INFO] finished tweaking crates.io crate bigint 4.4.3
[INFO] tweaked toml for crates.io crate bigint 4.4.3 written to /workspace/builds/worker-4-tc1/source/Cargo.toml
[INFO] crate crates.io crate bigint 4.4.3 already has a lockfile, it will not be regenerated
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded rand v0.3.23
[INFO] [stderr]   Downloaded quote v1.0.4
[INFO] [stderr]   Downloaded env_logger v0.3.5
[INFO] [stderr]   Downloaded rustc-hex v1.0.0
[INFO] [stderr]   Downloaded proc-macro2 v1.0.12
[INFO] [stderr]   Downloaded crunchy v0.1.6
[INFO] [stderr]   Downloaded memchr v0.1.11
[INFO] [stderr]   Downloaded thread-id v2.0.0
[INFO] [stderr]   Downloaded heapsize v0.4.2
[INFO] [stderr]   Downloaded utf8-ranges v0.1.3
[INFO] [stderr]   Downloaded thread_local v0.2.7
[INFO] [stderr]   Downloaded regex-syntax v0.3.9
[INFO] [stderr]   Downloaded quickcheck v0.4.1
[INFO] [stderr]   Downloaded aho-corasick v0.5.3
[INFO] [stderr]   Downloaded libc v0.2.69
[INFO] [stderr]   Downloaded regex v0.1.80
[INFO] [stderr]   Downloaded syn v1.0.19
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/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:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] b714bbf12835b5327d8cd28ec1acf0147abcf3b241e0a1a539c9f6f3477f83b9
[INFO] running `Command { std: "docker" "start" "-a" "b714bbf12835b5327d8cd28ec1acf0147abcf3b241e0a1a539c9f6f3477f83b9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "b714bbf12835b5327d8cd28ec1acf0147abcf3b241e0a1a539c9f6f3477f83b9", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "b714bbf12835b5327d8cd28ec1acf0147abcf3b241e0a1a539c9f6f3477f83b9", kill_on_drop: false }`
[INFO] [stdout] b714bbf12835b5327d8cd28ec1acf0147abcf3b241e0a1a539c9f6f3477f83b9
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 5568ff91002c7b6795f2b7e432f669fc9432e24623821b7b4143acd93815bbf6
[INFO] running `Command { std: "docker" "start" "-a" "5568ff91002c7b6795f2b7e432f669fc9432e24623821b7b4143acd93815bbf6", kill_on_drop: false }`
[INFO] [stderr]    Compiling crunchy v0.1.6
[INFO] [stderr]    Compiling byteorder v1.3.4
[INFO] [stderr]    Compiling bigint v4.4.3 (/opt/rustwide/workdir)
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: `#[warn(semicolon_in_expressions_from_macros)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:143:76
[INFO] [stdout]     |
[INFO] [stdout] 143 |         uint_full_mul_reg!($name, 8, $self_expr, $other, |a, b| a != 0 || b != 0);
[INFO] [stdout]     |                                                                                  ^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 984 |         U512(uint_full_mul_reg!(U256, 4, self, other))
[INFO] [stdout]     |              ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: `#[warn(invalid_value)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 22 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.21s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: bigint v4.4.3 (/opt/rustwide/workdir)
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`
[INFO] running `Command { std: "docker" "inspect" "5568ff91002c7b6795f2b7e432f669fc9432e24623821b7b4143acd93815bbf6", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "5568ff91002c7b6795f2b7e432f669fc9432e24623821b7b4143acd93815bbf6", kill_on_drop: false }`
[INFO] [stdout] 5568ff91002c7b6795f2b7e432f669fc9432e24623821b7b4143acd93815bbf6
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] be51800c2ca991959e40e7c580261410b96951d95400a5f7d8f45306dcdad92c
[INFO] running `Command { std: "docker" "start" "-a" "be51800c2ca991959e40e7c580261410b96951d95400a5f7d8f45306dcdad92c", kill_on_drop: false }`
[INFO] [stderr]    Compiling libc v0.2.69
[INFO] [stderr]    Compiling winapi-build v0.1.1
[INFO] [stderr]    Compiling winapi v0.2.8
[INFO] [stderr]    Compiling log v0.4.8
[INFO] [stderr]    Compiling utf8-ranges v0.1.3
[INFO] [stderr]    Compiling regex-syntax v0.3.9
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: `#[warn(semicolon_in_expressions_from_macros)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:143:76
[INFO] [stdout]     |
[INFO] [stdout] 143 |         uint_full_mul_reg!($name, 8, $self_expr, $other, |a, b| a != 0 || b != 0);
[INFO] [stdout]     |                                                                                  ^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 984 |         U512(uint_full_mul_reg!(U256, 4, self, other))
[INFO] [stdout]     |              ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: `#[warn(invalid_value)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 22 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Compiling kernel32-sys v0.2.2
[INFO] [stderr]    Compiling log v0.3.9
[INFO] [stderr]    Compiling memchr v0.1.11
[INFO] [stderr]    Compiling thread-id v2.0.0
[INFO] [stderr]    Compiling rand v0.4.6
[INFO] [stderr]    Compiling thread_local v0.2.7
[INFO] [stderr]    Compiling aho-corasick v0.5.3
[INFO] [stderr]    Compiling regex v0.1.80
[INFO] [stderr]    Compiling rand v0.3.23
[INFO] [stderr]    Compiling env_logger v0.3.5
[INFO] [stderr]    Compiling quickcheck v0.4.1
[INFO] [stderr]    Compiling bigint v4.4.3 (/opt/rustwide/workdir)
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: `#[warn(semicolon_in_expressions_from_macros)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:143:76
[INFO] [stdout]     |
[INFO] [stdout] 143 |         uint_full_mul_reg!($name, 8, $self_expr, $other, |a, b| a != 0 || b != 0);
[INFO] [stdout]     |                                                                                  ^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stdout]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:951:5
[INFO] [stdout]     |
[INFO] [stdout] 951 |                 try!(write!(f, "0x"));
[INFO] [stdout]     |                 ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stdout]    --> src/uint.rs:958:8
[INFO] [stdout]     |
[INFO] [stdout] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stdout]     |                             ^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: trailing semicolon in macro used in expression position
[INFO] [stdout]    --> src/uint.rs:146:71
[INFO] [stdout]     |
[INFO] [stdout] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stdout]     |                                                                             ^
[INFO] [stdout] ...
[INFO] [stdout] 984 |         U512(uint_full_mul_reg!(U256, 4, self, other))
[INFO] [stdout]     |              ---------------------------------------- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stdout]     = note: this warning originates in the macro `uint_full_mul_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stdout]    --> src/uint.rs:85:39
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                             ^^^^^^^^^^^^^
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the feature `alloc` has been stable since 1.36.0 and no longer requires an attribute to enable
[INFO] [stdout]   --> src/lib.rs:12:52
[INFO] [stdout]    |
[INFO] [stdout] 12 | #![cfg_attr(all(not(feature="std"), test), feature(alloc))]
[INFO] [stdout]    |                                                    ^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(stable_features)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: `#[warn(invalid_value)]` on by default
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 975 | construct_uint!(U128, 2);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 976 | construct_uint!(U256, 4);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stdout]    --> src/uint.rs:85:26
[INFO] [stdout]     |
[INFO] [stdout] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stdout]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |                                |
[INFO] [stdout]     |                                this code causes undefined behavior when executed
[INFO] [stdout]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stdout] ...
[INFO] [stdout] 977 | construct_uint!(U512, 8);
[INFO] [stdout]     | ------------------------ in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: integers must be initialized
[INFO] [stdout]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 23 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 5.41s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: bigint v4.4.3 (/opt/rustwide/workdir)
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 2`
[INFO] running `Command { std: "docker" "inspect" "be51800c2ca991959e40e7c580261410b96951d95400a5f7d8f45306dcdad92c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "be51800c2ca991959e40e7c580261410b96951d95400a5f7d8f45306dcdad92c", kill_on_drop: false }`
[INFO] [stdout] be51800c2ca991959e40e7c580261410b96951d95400a5f7d8f45306dcdad92c
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:59a85a07ab18ca8720692f8e61effa1c651d9e2ca591e072c2b212bb91a6b8b5" "/opt/rustwide/cargo-home/bin/cargo" "+1871252fc8bb672d40787e67404e6eaae7059369" "test" "--frozen", kill_on_drop: false }`
[INFO] [stdout] e91877808020dedee8db46de3c73f36685089cfe48cf1f7841df119cf6f572bd
[INFO] running `Command { std: "docker" "start" "-a" "e91877808020dedee8db46de3c73f36685089cfe48cf1f7841df119cf6f572bd", kill_on_drop: false }`
[INFO] [stderr] warning: trailing semicolon in macro used in expression position
[INFO] [stderr]    --> src/uint.rs:146:71
[INFO] [stderr]     |
[INFO] [stderr] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stderr]     |                                                                             ^
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stderr]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stderr]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stderr]     = note: `#[warn(semicolon_in_expressions_from_macros)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:951:5
[INFO] [stderr]     |
[INFO] [stderr] 951 |                 try!(write!(f, "0x"));
[INFO] [stderr]     |                 ^^^
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: `#[warn(deprecated)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:958:8
[INFO] [stderr]     |
[INFO] [stderr] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stderr]     |                             ^^^
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: trailing semicolon in macro used in expression position
[INFO] [stderr]    --> src/uint.rs:146:71
[INFO] [stderr]     |
[INFO] [stderr] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stderr]     |                                                                             ^
[INFO] [stderr] ...
[INFO] [stderr] 976 | construct_uint!(U256, 4);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stderr]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stderr]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stderr]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:951:5
[INFO] [stderr]     |
[INFO] [stderr] 951 |                 try!(write!(f, "0x"));
[INFO] [stderr]     |                 ^^^
[INFO] [stderr] ...
[INFO] [stderr] 976 | construct_uint!(U256, 4);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:958:8
[INFO] [stderr]     |
[INFO] [stderr] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stderr]     |                             ^^^
[INFO] [stderr] ...
[INFO] [stderr] 976 | construct_uint!(U256, 4);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: trailing semicolon in macro used in expression position
[INFO] [stderr]    --> src/uint.rs:143:76
[INFO] [stderr]     |
[INFO] [stderr] 143 |         uint_full_mul_reg!($name, 8, $self_expr, $other, |a, b| a != 0 || b != 0);
[INFO] [stderr]     |                                                                                  ^
[INFO] [stderr] ...
[INFO] [stderr] 977 | construct_uint!(U512, 8);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stderr]     = note: macro invocations at the end of a block are treated as expressions
[INFO] [stderr]     = note: to ignore the value produced by the macro, add a semicolon after the invocation of `uint_full_mul_reg`
[INFO] [stderr]     = note: this warning originates in the macro `uint_full_mul_reg` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:951:5
[INFO] [stderr]     |
[INFO] [stderr] 951 |                 try!(write!(f, "0x"));
[INFO] [stderr]     |                 ^^^
[INFO] [stderr] ...
[INFO] [stderr] 977 | construct_uint!(U512, 8);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated macro `try`: use the `?` operator instead
[INFO] [stderr]    --> src/uint.rs:958:8
[INFO] [stderr]     |
[INFO] [stderr] 958 |                             try!(write!(f, "{:x}", nibble));
[INFO] [stderr]     |                             ^^^
[INFO] [stderr] ...
[INFO] [stderr] 977 | construct_uint!(U512, 8);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: trailing semicolon in macro used in expression position
[INFO] [stderr]    --> src/uint.rs:146:71
[INFO] [stderr]     |
[INFO] [stderr] 146 |         uint_full_mul_reg!($name, $n_words, $self_expr, $other, |_, _| true);
[INFO] [stderr]     |                                                                             ^
[INFO] [stderr] ...
[INFO] [stderr] 984 |         U512(uint_full_mul_reg!(U256, 4, self, other))
[INFO] [stderr]     |              ---------------------------------------- in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stderr]     = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
[INFO] [stderr]     = note: this warning originates in the macro `uint_full_mul_reg` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stderr]    --> src/uint.rs:85:39
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                             ^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stderr]    --> src/uint.rs:85:39
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                             ^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 976 | construct_uint!(U256, 4);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: use of deprecated function `core::mem::uninitialized`: use `mem::MaybeUninit` instead
[INFO] [stderr]    --> src/uint.rs:85:39
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                             ^^^^^^^^^^^^^
[INFO] [stderr] ...
[INFO] [stderr] 977 | construct_uint!(U512, 8);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stderr]    --> src/uint.rs:85:26
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |                                |
[INFO] [stderr]     |                                this code causes undefined behavior when executed
[INFO] [stderr]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: integers must be initialized
[INFO] [stderr]     = note: `#[warn(invalid_value)]` on by default
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: the type `[u64; 2]` does not permit being left uninitialized
[INFO] [stderr]    --> src/uint.rs:85:26
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |                                |
[INFO] [stderr]     |                                this code causes undefined behavior when executed
[INFO] [stderr]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stderr] ...
[INFO] [stderr] 975 | construct_uint!(U128, 2);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: integers must be initialized
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: the type `[u64; 4]` does not permit being left uninitialized
[INFO] [stderr]    --> src/uint.rs:85:26
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |                                |
[INFO] [stderr]     |                                this code causes undefined behavior when executed
[INFO] [stderr]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stderr] ...
[INFO] [stderr] 976 | construct_uint!(U256, 4);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: integers must be initialized
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: the type `[u64; 8]` does not permit being left uninitialized
[INFO] [stderr]    --> src/uint.rs:85:26
[INFO] [stderr]     |
[INFO] [stderr] 85  |         let mut ret = unsafe { ::core::mem::uninitialized() };
[INFO] [stderr]     |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stderr]     |                                |
[INFO] [stderr]     |                                this code causes undefined behavior when executed
[INFO] [stderr]     |                                help: use `MaybeUninit<T>` instead, and only call `assume_init` after initialization is done
[INFO] [stderr] ...
[INFO] [stderr] 977 | construct_uint!(U512, 8);
[INFO] [stderr]     | ------------------------ in this macro invocation
[INFO] [stderr]     |
[INFO] [stderr]     = note: integers must be initialized
[INFO] [stderr]     = note: this warning originates in the macro `uint_overflowing_binop` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stderr] 
[INFO] [stderr] warning: `bigint` (lib) generated 22 warnings (5 duplicates)
[INFO] [stderr] warning: the feature `alloc` has been stable since 1.36.0 and no longer requires an attribute to enable
[INFO] [stderr]   --> src/lib.rs:12:52
[INFO] [stderr]    |
[INFO] [stderr] 12 | #![cfg_attr(all(not(feature="std"), test), feature(alloc))]
[INFO] [stderr]    |                                                    ^^^^^
[INFO] [stderr]    |
[INFO] [stderr]    = note: `#[warn(stable_features)]` on by default
[INFO] [stderr] 
[INFO] [stderr] warning: `bigint` (lib test) generated 23 warnings (22 duplicates)
[INFO] [stderr]     Finished `test` profile [unoptimized + debuginfo] target(s) in 0.06s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: bigint v4.4.3 (/opt/rustwide/workdir)
[INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 2`
[INFO] [stderr]      Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/bigint-2d793335d187ad0e)
[INFO] [stdout] 
[INFO] [stdout] running 3 tests
[INFO] [stdout] test uint::tests::display_u128 ... ok
[INFO] [stdout] test uint::tests::display_u256 ... ok
[INFO] [stdout] test uint::tests::display_u512 ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.08s
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests bigint
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
[INFO] [stdout] 
[INFO] running `Command { std: "docker" "inspect" "e91877808020dedee8db46de3c73f36685089cfe48cf1f7841df119cf6f572bd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e91877808020dedee8db46de3c73f36685089cfe48cf1f7841df119cf6f572bd", kill_on_drop: false }`
[INFO] [stdout] e91877808020dedee8db46de3c73f36685089cfe48cf1f7841df119cf6f572bd
