[INFO] fetching crate rustls-webpki 0.102.8...
[INFO] checking rustls-webpki-0.102.8 against try#da25749bf5e6ba5ed862ff361c19afff2a986b2d for pr-132712
[INFO] extracting crate rustls-webpki 0.102.8 into /workspace/builds/worker-4-tc2/source
[INFO] validating manifest of crates.io crate rustls-webpki 0.102.8 on toolchain da25749bf5e6ba5ed862ff361c19afff2a986b2d
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+da25749bf5e6ba5ed862ff361c19afff2a986b2d" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate rustls-webpki 0.102.8
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate rustls-webpki 0.102.8
[INFO] tweaked toml for crates.io crate rustls-webpki 0.102.8 written to /workspace/builds/worker-4-tc2/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+da25749bf5e6ba5ed862ff361c19afff2a986b2d" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 77 packages to latest compatible versions
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+da25749bf5e6ba5ed862ff361c19afff2a986b2d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+da25749bf5e6ba5ed862ff361c19afff2a986b2d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] a14e27d4faaeaa2fc55e33b3c23f018dc4c454d2db7dbe0bc900f7187535d493
[INFO] running `Command { std: "docker" "start" "-a" "a14e27d4faaeaa2fc55e33b3c23f018dc4c454d2db7dbe0bc900f7187535d493", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "a14e27d4faaeaa2fc55e33b3c23f018dc4c454d2db7dbe0bc900f7187535d493", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "a14e27d4faaeaa2fc55e33b3c23f018dc4c454d2db7dbe0bc900f7187535d493", kill_on_drop: false }`
[INFO] [stdout] a14e27d4faaeaa2fc55e33b3c23f018dc4c454d2db7dbe0bc900f7187535d493
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=allow" "-e" "RUSTDOCFLAGS=--cap-lints=allow" "-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:4a844ea9eb2546a2d2c7022eacef16ef2e8229c7fbb2c7d4d55a9ceca922f72d" "/opt/rustwide/cargo-home/bin/cargo" "+da25749bf5e6ba5ed862ff361c19afff2a986b2d" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 4e56503a04c64bcbbc824f753be73f74a34c1207d54a5c0b2a9cf6ecc679836c
[INFO] running `Command { std: "docker" "start" "-a" "4e56503a04c64bcbbc824f753be73f74a34c1207d54a5c0b2a9cf6ecc679836c", kill_on_drop: false }`
[INFO] [stderr] Copying to /tmp/fixit
[INFO] [stderr] Running `cargo fix --edition`
[INFO] [stderr]    Migrating Cargo.toml from 2021 edition to 2024
[INFO] [stderr]    Compiling pkg-config v0.3.31
[INFO] [stderr]    Compiling aws-lc-rs v1.10.0
[INFO] [stderr]     Checking rustls-pki-types v1.10.0
[INFO] [stderr]     Checking zeroize v1.8.1
[INFO] [stderr]     Checking spin v0.9.8
[INFO] [stderr]     Checking untrusted v0.7.1
[INFO] [stderr]     Checking getrandom v0.2.15
[INFO] [stderr]     Checking time v0.3.36
[INFO] [stderr]     Checking bencher v0.1.5
[INFO] [stderr]    Compiling cmake v0.1.51
[INFO] [stderr]    Compiling ring v0.17.8
[INFO] [stderr]    Compiling aws-lc-sys v0.22.0
[INFO] [stderr]    Compiling bzip2-sys v0.1.11+1.0.8
[INFO] [stderr]     Checking yasna v0.5.2
[INFO] [stderr]     Checking bzip2 v0.4.4
[INFO] [stderr]     Checking rustls-webpki v0.102.8 (/tmp/fixit)
[INFO] [stderr]    Migrating src/lib.rs from 2021 edition to 2024
[INFO] [stderr]        Fixed src/der.rs (3 fixes)
[INFO] [stderr]        Fixed src/cert.rs (1 fix)
[INFO] [stderr]     Checking rcgen v0.13.1
[INFO] [stderr]    Migrating tests/cert_v1_unsupported.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/tls_server_certs.rs from 2021 edition to 2024
[INFO] [stdout] error[E0583]: file not found for module `test_utils`
[INFO] [stdout]   --> src/lib.rs:71:1
[INFO] [stdout]    |
[INFO] [stdout] 71 | pub(crate) mod test_utils;
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: to create the module `test_utils`, create file "src/test_utils.rs" or "src/test_utils/mod.rs"
[INFO] [stdout]    = note: if there is a `mod test_utils` elsewhere in the crate already, import it with `use crate::...` instead
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-spki-params-null.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 147 | / test_verify_signed_data!(
[INFO] [stdout] 148 | |     test_ecdsa_prime256v1_sha512_spki_params_null,
[INFO] [stdout] 149 | |     "ecdsa-prime256v1-sha512-spki-params-null.pem",
[INFO] [stdout] 150 | |     Err(UNSUPPORTED_ECDSA_SHA512_SIGNATURE)
[INFO] [stdout] 151 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-unused-bits-signature.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 152 | / test_verify_signed_data_signature_outer!(
[INFO] [stdout] 153 | |     test_ecdsa_prime256v1_sha512_unused_bits_signature,
[INFO] [stdout] 154 | |     "ecdsa-prime256v1-sha512-unused-bits-signature.pem",
[INFO] [stdout] 155 | |     Error::BadDer
[INFO] [stdout] 156 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data_signature_outer` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-using-ecdh-key.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 159 | / test_verify_signed_data!(
[INFO] [stdout] 160 | |     test_ecdsa_prime256v1_sha512_using_ecdh_key,
[INFO] [stdout] 161 | |     "ecdsa-prime256v1-sha512-using-ecdh-key.pem",
[INFO] [stdout] 162 | |     Err(UNSUPPORTED_ECDSA_SHA512_SIGNATURE)
[INFO] [stdout] 163 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-using-ecmqv-key.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 166 | / test_verify_signed_data!(
[INFO] [stdout] 167 | |     test_ecdsa_prime256v1_sha512_using_ecmqv_key,
[INFO] [stdout] 168 | |     "ecdsa-prime256v1-sha512-using-ecmqv-key.pem",
[INFO] [stdout] 169 | |     Err(UNSUPPORTED_ECDSA_SHA512_SIGNATURE)
[INFO] [stdout] 170 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-using-rsa-algorithm.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 171 | / test_verify_signed_data!(
[INFO] [stdout] 172 | |     test_ecdsa_prime256v1_sha512_using_rsa_algorithm,
[INFO] [stdout] 173 | |     "ecdsa-prime256v1-sha512-using-rsa-algorithm.pem",
[INFO] [stdout] 174 | |     Err(UNSUPPORTED_SIGNATURE_ALGORITHM_FOR_RSA_KEY)
[INFO] [stdout] 175 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512-wrong-signature-format.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 178 | / test_verify_signed_data!(
[INFO] [stdout] 179 | |     test_ecdsa_prime256v1_sha512_wrong_signature_format,
[INFO] [stdout] 180 | |     "ecdsa-prime256v1-sha512-wrong-signature-format.pem",
[INFO] [stdout] 181 | |     Err(UNSUPPORTED_ECDSA_SHA512_SIGNATURE)
[INFO] [stdout] 182 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-prime256v1-sha512.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 184 | / test_verify_signed_data!(
[INFO] [stdout] 185 | |     test_ecdsa_prime256v1_sha512,
[INFO] [stdout] 186 | |     "ecdsa-prime256v1-sha512.pem",
[INFO] [stdout] 187 | |     Err(UNSUPPORTED_ECDSA_SHA512_SIGNATURE)
[INFO] [stdout] 188 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-secp384r1-sha256-corrupted-data.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 189 | / test_verify_signed_data!(
[INFO] [stdout] 190 | |     test_ecdsa_secp384r1_sha256_corrupted_data,
[INFO] [stdout] 191 | |     "ecdsa-secp384r1-sha256-corrupted-data.pem",
[INFO] [stdout] 192 | |     Err(Error::InvalidSignatureForPublicKey)
[INFO] [stdout] 193 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-secp384r1-sha256.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 194 | / test_verify_signed_data!(
[INFO] [stdout] 195 | |     test_ecdsa_secp384r1_sha256,
[INFO] [stdout] 196 | |     "ecdsa-secp384r1-sha256.pem",
[INFO] [stdout] 197 | |     Ok(())
[INFO] [stdout] 198 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ecdsa-using-rsa-key.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 199 | / test_verify_signed_data!(
[INFO] [stdout] 200 | |     test_ecdsa_using_rsa_key,
[INFO] [stdout] 201 | |     "ecdsa-using-rsa-key.pem",
[INFO] [stdout] 202 | |     Err(Error::UnsupportedSignatureAlgorithmForPublicKey)
[INFO] [stdout] 203 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1-bad-key-der-length.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 205 | / test_parse_spki_bad_outer!(
[INFO] [stdout] 206 | |     test_rsa_pkcs1_sha1_bad_key_der_length,
[INFO] [stdout] 207 | |     "rsa-pkcs1-sha1-bad-key-der-length.pem",
[INFO] [stdout] 208 | |     Error::BadDer
[INFO] [stdout] 209 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_parse_spki_bad_outer` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1-bad-key-der-null.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 210 | / test_parse_spki_bad_outer!(
[INFO] [stdout] 211 | |     test_rsa_pkcs1_sha1_bad_key_der_null,
[INFO] [stdout] 212 | |     "rsa-pkcs1-sha1-bad-key-der-null.pem",
[INFO] [stdout] 213 | |     Error::BadDer
[INFO] [stdout] 214 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_parse_spki_bad_outer` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1-key-params-absent.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 215 | / test_verify_signed_data!(
[INFO] [stdout] 216 | |     test_rsa_pkcs1_sha1_key_params_absent,
[INFO] [stdout] 217 | |     "rsa-pkcs1-sha1-key-params-absent.pem",
[INFO] [stdout] 218 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 219 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1-using-pss-key-no-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 220 | / test_verify_signed_data!(
[INFO] [stdout] 221 | |     test_rsa_pkcs1_sha1_using_pss_key_no_params,
[INFO] [stdout] 222 | |     "rsa-pkcs1-sha1-using-pss-key-no-params.pem",
[INFO] [stdout] 223 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 224 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1-wrong-algorithm.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 225 | / test_verify_signed_data!(
[INFO] [stdout] 226 | |     test_rsa_pkcs1_sha1_wrong_algorithm,
[INFO] [stdout] 227 | |     "rsa-pkcs1-sha1-wrong-algorithm.pem",
[INFO] [stdout] 228 | |     Err(INVALID_SIGNATURE_FOR_RSA_KEY)
[INFO] [stdout] 229 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha1.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 230 | / test_verify_signed_data!(
[INFO] [stdout] 231 | |     test_rsa_pkcs1_sha1,
[INFO] [stdout] 232 | |     "rsa-pkcs1-sha1.pem",
[INFO] [stdout] 233 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 234 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha256.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 239 | / test_verify_signed_data!(
[INFO] [stdout] 240 | |     test_rsa_pkcs1_sha256,
[INFO] [stdout] 241 | |     "rsa-pkcs1-sha256.pem",
[INFO] [stdout] 242 | |     Err(INVALID_SIGNATURE_FOR_RSA_KEY)
[INFO] [stdout] 243 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha256-key-encoded-ber.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 244 | / test_parse_spki_bad_outer!(
[INFO] [stdout] 245 | |     test_rsa_pkcs1_sha256_key_encoded_ber,
[INFO] [stdout] 246 | |     "rsa-pkcs1-sha256-key-encoded-ber.pem",
[INFO] [stdout] 247 | |     Error::BadDer
[INFO] [stdout] 248 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_parse_spki_bad_outer` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha256-spki-non-null-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 249 | / test_verify_signed_data!(
[INFO] [stdout] 250 | |     test_rsa_pkcs1_sha256_spki_non_null_params,
[INFO] [stdout] 251 | |     "rsa-pkcs1-sha256-spki-non-null-params.pem",
[INFO] [stdout] 252 | |     Err(UNSUPPORTED_SIGNATURE_ALGORITHM_FOR_RSA_KEY)
[INFO] [stdout] 253 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha256-using-ecdsa-algorithm.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 254 | / test_verify_signed_data!(
[INFO] [stdout] 255 | |     test_rsa_pkcs1_sha256_using_ecdsa_algorithm,
[INFO] [stdout] 256 | |     "rsa-pkcs1-sha256-using-ecdsa-algorithm.pem",
[INFO] [stdout] 257 | |     Err(Error::UnsupportedSignatureAlgorithmForPublicKey)
[INFO] [stdout] 258 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pkcs1-sha256-using-id-ea-rsa.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 259 | / test_verify_signed_data!(
[INFO] [stdout] 260 | |     test_rsa_pkcs1_sha256_using_id_ea_rsa,
[INFO] [stdout] 261 | |     "rsa-pkcs1-sha256-using-id-ea-rsa.pem",
[INFO] [stdout] 262 | |     Err(UNSUPPORTED_SIGNATURE_ALGORITHM_FOR_RSA_KEY)
[INFO] [stdout] 263 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha1-salt20-using-pss-key-no-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 266 | / test_verify_signed_data!(
[INFO] [stdout] 267 | |     test_rsa_pss_sha1_salt20_using_pss_key_no_params,
[INFO] [stdout] 268 | |     "rsa-pss-sha1-salt20-using-pss-key-no-params.pem",
[INFO] [stdout] 269 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 270 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha1-salt20-using-pss-key-with-null-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 271 | / test_verify_signed_data!(
[INFO] [stdout] 272 | |     test_rsa_pss_sha1_salt20_using_pss_key_with_null_params,
[INFO] [stdout] 273 | |     "rsa-pss-sha1-salt20-using-pss-key-with-null-params.pem",
[INFO] [stdout] 274 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 275 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha1-salt20.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 276 | / test_verify_signed_data!(
[INFO] [stdout] 277 | |     test_rsa_pss_sha1_salt20,
[INFO] [stdout] 278 | |     "rsa-pss-sha1-salt20.pem",
[INFO] [stdout] 279 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 280 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha1-wrong-salt.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 281 | / test_verify_signed_data!(
[INFO] [stdout] 282 | |     test_rsa_pss_sha1_wrong_salt,
[INFO] [stdout] 283 | |     "rsa-pss-sha1-wrong-salt.pem",
[INFO] [stdout] 284 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 285 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha256-mgf1-sha512-salt33.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 286 | / test_verify_signed_data!(
[INFO] [stdout] 287 | |     test_rsa_pss_sha256_mgf1_sha512_salt33,
[INFO] [stdout] 288 | |     "rsa-pss-sha256-mgf1-sha512-salt33.pem",
[INFO] [stdout] 289 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 290 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha256-salt10-using-pss-key-with-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 291 | / test_verify_signed_data!(
[INFO] [stdout] 292 | |     test_rsa_pss_sha256_salt10_using_pss_key_with_params,
[INFO] [stdout] 293 | |     "rsa-pss-sha256-salt10-using-pss-key-with-params.pem",
[INFO] [stdout] 294 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 295 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha256-salt10-using-pss-key-with-wrong-params.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 296 | / test_verify_signed_data!(
[INFO] [stdout] 297 | |     test_rsa_pss_sha256_salt10_using_pss_key_with_wrong_params,
[INFO] [stdout] 298 | |     "rsa-pss-sha256-salt10-using-pss-key-with-wrong-params.pem",
[INFO] [stdout] 299 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 300 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-pss-sha256-salt10.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 301 | / test_verify_signed_data!(
[INFO] [stdout] 302 | |     test_rsa_pss_sha256_salt10,
[INFO] [stdout] 303 | |     "rsa-pss-sha256-salt10.pem",
[INFO] [stdout] 304 | |     Err(Error::UnsupportedSignatureAlgorithm)
[INFO] [stdout] 305 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha256-salt32.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 308 | / test_verify_signed_data!(
[INFO] [stdout] 309 | |     test_rsa_pss_sha256_salt32,
[INFO] [stdout] 310 | |     "ours/rsa-pss-sha256-salt32.pem",
[INFO] [stdout] 311 | |     OK_IF_RSA_AVAILABLE
[INFO] [stdout] 312 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha384-salt48.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 313 | / test_verify_signed_data!(
[INFO] [stdout] 314 | |     test_rsa_pss_sha384_salt48,
[INFO] [stdout] 315 | |     "ours/rsa-pss-sha384-salt48.pem",
[INFO] [stdout] 316 | |     OK_IF_RSA_AVAILABLE
[INFO] [stdout] 317 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha512-salt64.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 318 | / test_verify_signed_data!(
[INFO] [stdout] 319 | |     test_rsa_pss_sha512_salt64,
[INFO] [stdout] 320 | |     "ours/rsa-pss-sha512-salt64.pem",
[INFO] [stdout] 321 | |     OK_IF_RSA_AVAILABLE
[INFO] [stdout] 322 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha256-salt32-corrupted-data.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 323 | / test_verify_signed_data!(
[INFO] [stdout] 324 | |     test_rsa_pss_sha256_salt32_corrupted_data,
[INFO] [stdout] 325 | |     "ours/rsa-pss-sha256-salt32-corrupted-data.pem",
[INFO] [stdout] 326 | |     Err(INVALID_SIGNATURE_FOR_RSA_KEY)
[INFO] [stdout] 327 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha384-salt48-corrupted-data.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 328 | / test_verify_signed_data!(
[INFO] [stdout] 329 | |     test_rsa_pss_sha384_salt48_corrupted_data,
[INFO] [stdout] 330 | |     "ours/rsa-pss-sha384-salt48-corrupted-data.pem",
[INFO] [stdout] 331 | |     Err(INVALID_SIGNATURE_FOR_RSA_KEY)
[INFO] [stdout] 332 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/rsa-pss-sha512-salt64-corrupted-data.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 333 | / test_verify_signed_data!(
[INFO] [stdout] 334 | |     test_rsa_pss_sha512_salt64_corrupted_data,
[INFO] [stdout] 335 | |     "ours/rsa-pss-sha512-salt64-corrupted-data.pem",
[INFO] [stdout] 336 | |     Err(INVALID_SIGNATURE_FOR_RSA_KEY)
[INFO] [stdout] 337 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa-using-ec-key.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 339 | / test_verify_signed_data!(
[INFO] [stdout] 340 | |     test_rsa_using_ec_key,
[INFO] [stdout] 341 | |     "rsa-using-ec-key.pem",
[INFO] [stdout] 342 | |     Err(UNSUPPORTED_SIGNATURE_ALGORITHM_FOR_RSA_KEY)
[INFO] [stdout] 343 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/rsa2048-pkcs1-sha512.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 344 | / test_verify_signed_data!(
[INFO] [stdout] 345 | |     test_rsa2048_pkcs1_sha512,
[INFO] [stdout] 346 | |     "rsa2048-pkcs1-sha512.pem",
[INFO] [stdout] 347 | |     OK_IF_RSA_AVAILABLE
[INFO] [stdout] 348 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/ecdsa-prime256v1-sha256.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 350 | / test_verify_signed_data!(
[INFO] [stdout] 351 | |     test_ecdsa_prime256v1_sha256,
[INFO] [stdout] 352 | |     "ours/ecdsa-prime256v1-sha256.pem",
[INFO] [stdout] 353 | |     Ok(())
[INFO] [stdout] 354 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/ecdsa-prime256v1-sha256-compressed.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 355 | / test_verify_signed_data!(
[INFO] [stdout] 356 | |     test_ecdsa_prime256v1_sha256_compressed,
[INFO] [stdout] 357 | |     "ours/ecdsa-prime256v1-sha256-compressed.pem",
[INFO] [stdout] 358 | |     OK_IF_POINT_COMPRESSION_SUPPORTED
[INFO] [stdout] 359 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: couldn't read `src/../third-party/chromium/data/verify_signed_data/ours/ecdsa-prime256v1-sha256-spki-inside-spki.pem`: No such file or directory (os error 2)
[INFO] [stdout]    --> src/./alg_tests.rs:33:9
[INFO] [stdout]     |
[INFO] [stdout] 33  | /         include_bytes!(concat!(
[INFO] [stdout] 34  | |             "../third-party/chromium/data/verify_signed_data/",
[INFO] [stdout] 35  | |             $file_name
[INFO] [stdout] 36  | |         ))
[INFO] [stdout]     | |__________^
[INFO] [stdout] ...
[INFO] [stdout] 360 | / test_verify_signed_data!(
[INFO] [stdout] 361 | |     test_ecdsa_prime256v1_sha256_spki_inside_spki,
[INFO] [stdout] 362 | |     "ours/ecdsa-prime256v1-sha256-spki-inside-spki.pem",
[INFO] [stdout] 363 | |     Err(Error::InvalidSignatureForPublicKey)
[INFO] [stdout] 364 | | );
[INFO] [stdout]     | |_- in this macro invocation
[INFO] [stdout]     |
[INFO] [stdout]     = note: this error originates in the macro `include_bytes` which comes from the expansion of the macro `test_verify_signed_data` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `crate::test_utils::RCGEN_SIGNATURE_ALG`
[INFO] [stdout]    --> src/end_entity.rs:190:9
[INFO] [stdout]     |
[INFO] [stdout] 190 |     use crate::test_utils::RCGEN_SIGNATURE_ALG;
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `RCGEN_SIGNATURE_ALG` in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved imports `crate::test_utils::issuer_params`, `crate::test_utils::make_end_entity`, `crate::test_utils::make_issuer`
[INFO] [stdout]    --> src/verify_cert.rs:702:29
[INFO] [stdout]     |
[INFO] [stdout] 702 |     use crate::test_utils::{issuer_params, make_end_entity, make_issuer};
[INFO] [stdout]     |                             ^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^  ^^^^^^^^^^^ no `make_issuer` in `test_utils`
[INFO] [stdout]     |                             |              |
[INFO] [stdout]     |                             |              no `make_end_entity` in `test_utils`
[INFO] [stdout]     |                             no `issuer_params` in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `make_issuer` in module `test_utils`
[INFO] [stdout]    --> src/end_entity.rs:200:34
[INFO] [stdout]     |
[INFO] [stdout] 200 |         let issuer = test_utils::make_issuer("Test");
[INFO] [stdout]     |                                  ^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find function `end_entity_params` in module `test_utils`
[INFO] [stdout]    --> src/end_entity.rs:203:42
[INFO] [stdout]     |
[INFO] [stdout] 203 |             let mut params = test_utils::end_entity_params(vec![DNS_NAME.to_string()]);
[INFO] [stdout]     |                                          ^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]    --> src/verify_cert.rs:762:61
[INFO] [stdout]     |
[INFO] [stdout] 762 |         let ca_key_pair = KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]     |                                                             ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]    --> src/verify_cert.rs:772:51
[INFO] [stdout]     |
[INFO] [stdout] 772 |                 KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]     |                                                   ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]    --> src/verify_cert.rs:885:67
[INFO] [stdout]     |
[INFO] [stdout] 885 |         let intermediate_a_kp = KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]     |                                                                   ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]    --> src/verify_cert.rs:897:67
[INFO] [stdout]     |
[INFO] [stdout] 897 |         let intermediate_c_kp = KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]     |                                                                   ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]    --> src/verify_cert.rs:910:68
[INFO] [stdout]     |
[INFO] [stdout] 910 |         let intermediate_b_key = KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]     |                                                                    ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find value `RCGEN_SIGNATURE_ALG` in module `test_utils`
[INFO] [stdout]     --> src/verify_cert.rs:1093:62
[INFO] [stdout]      |
[INFO] [stdout] 1093 |             let key_pair = KeyPair::generate_for(test_utils::RCGEN_SIGNATURE_ALG).unwrap();
[INFO] [stdout]      |                                                              ^^^^^^^^^^^^^^^^^^^ not found in `test_utils`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/./alg_tests.rs:32:18
[INFO] [stdout]    |
[INFO] [stdout] 32 |     ( $file_name:expr ) => {
[INFO] [stdout]    |                  ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout]    = note: `--force-warn edition-2024-expr-fragment-specifier` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 32 |     ( $file_name:expr_2021 ) => {
[INFO] [stdout]    |                  ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/./alg_tests.rs:43:33
[INFO] [stdout]    |
[INFO] [stdout] 43 |     ($fn_name:ident, $file_name:expr, $expected_result:expr) => {
[INFO] [stdout]    |                                 ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 43 |     ($fn_name:ident, $file_name:expr_2021, $expected_result:expr) => {
[INFO] [stdout]    |                                 ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]   --> src/./alg_tests.rs:43:56
[INFO] [stdout]    |
[INFO] [stdout] 43 |     ($fn_name:ident, $file_name:expr, $expected_result:expr) => {
[INFO] [stdout]    |                                                        ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = warning: this changes meaning in Rust 2024
[INFO] [stdout]    = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]    |
[INFO] [stdout] 43 |     ($fn_name:ident, $file_name:expr, $expected_result:expr_2021) => {
[INFO] [stdout]    |                                                        ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/./alg_tests.rs:100:33
[INFO] [stdout]     |
[INFO] [stdout] 100 |     ($fn_name:ident, $file_name:expr, $expected_result:expr) => {
[INFO] [stdout]     |                                 ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 100 |     ($fn_name:ident, $file_name:expr_2021, $expected_result:expr) => {
[INFO] [stdout]     |                                 ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/./alg_tests.rs:100:56
[INFO] [stdout]     |
[INFO] [stdout] 100 |     ($fn_name:ident, $file_name:expr, $expected_result:expr) => {
[INFO] [stdout]     |                                                        ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 100 |     ($fn_name:ident, $file_name:expr, $expected_result:expr_2021) => {
[INFO] [stdout]     |                                                        ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/./alg_tests.rs:123:33
[INFO] [stdout]     |
[INFO] [stdout] 123 |     ($fn_name:ident, $file_name:expr, $error:expr) => {
[INFO] [stdout]     |                                 ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 123 |     ($fn_name:ident, $file_name:expr_2021, $error:expr) => {
[INFO] [stdout]     |                                 ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: the `expr` fragment specifier will accept more expressions in the 2024 edition
[INFO] [stdout]    --> src/./alg_tests.rs:123:46
[INFO] [stdout]     |
[INFO] [stdout] 123 |     ($fn_name:ident, $file_name:expr, $error:expr) => {
[INFO] [stdout]     |                                              ^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see Migration Guide <https://doc.rust-lang.org/nightly/edition-guide/rust-2024/macro-fragment-specifiers.html>
[INFO] [stdout] help: to keep the existing behavior, use the `expr_2021` fragment specifier
[INFO] [stdout]     |
[INFO] [stdout] 123 |     ($fn_name:ident, $file_name:expr, $error:expr_2021) => {
[INFO] [stdout]     |                                              ~~~~~~~~~
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0425, E0432, E0583.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0425`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `rustls-webpki` (lib test) due to 51 previous errors; 7 warnings emitted
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stderr]    Migrating tests/crl_tests.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/client_auth_revocation.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/integration.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/better_tls.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/cert_without_extensions.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/client_auth.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/custom_ekus.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/signatures.rs from 2021 edition to 2024
[INFO] [stderr] error: failed to migrate to next edition
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `cargo fix --edition --allow-no-vcs --allow-dirty --frozen --all --all-targets --message-format=json` (exit status: 101)
[INFO] running `Command { std: "docker" "inspect" "4e56503a04c64bcbbc824f753be73f74a34c1207d54a5c0b2a9cf6ecc679836c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4e56503a04c64bcbbc824f753be73f74a34c1207d54a5c0b2a9cf6ecc679836c", kill_on_drop: false }`
[INFO] [stdout] 4e56503a04c64bcbbc824f753be73f74a34c1207d54a5c0b2a9cf6ecc679836c