[INFO] crate nom-peg 0.1.1 is already in cache [INFO] extracting crate nom-peg 0.1.1 into work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/nom-peg/0.1.1 [INFO] extracting crate nom-peg 0.1.1 into work/ex/pr-63565/sources/try#75eff020d0923c035c2fe220db4a0465cd847048/reg/nom-peg/0.1.1 [INFO] validating manifest of nom-peg-0.1.1 on toolchain master#c43d03a19f326f4a323569328cc501e86eb6d22e [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of nom-peg-0.1.1 on toolchain try#75eff020d0923c035c2fe220db4a0465cd847048 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing nom-peg-0.1.1 [INFO] finished frobbing nom-peg-0.1.1 [INFO] frobbed toml for nom-peg-0.1.1 written to work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/nom-peg/0.1.1/Cargo.toml [INFO] started frobbing nom-peg-0.1.1 [INFO] finished frobbing nom-peg-0.1.1 [INFO] frobbed toml for nom-peg-0.1.1 written to work/ex/pr-63565/sources/try#75eff020d0923c035c2fe220db4a0465cd847048/reg/nom-peg/0.1.1/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking nom-peg-0.1.1 against master#c43d03a19f326f4a323569328cc501e86eb6d22e for pr-63565 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-63565/worker-2/master#c43d03a19f326f4a323569328cc501e86eb6d22e:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/nom-peg/0.1.1:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] a9c8e4de10d7d7229937e34466ac9ee5aff188ab2662f13e16410bea29ca5b63 [INFO] running `"docker" "start" "-a" "a9c8e4de10d7d7229937e34466ac9ee5aff188ab2662f13e16410bea29ca5b63"` [INFO] [stderr] Compiling nom-peg v0.1.1 (/opt/crater/workdir) [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> tests/json.rs:25:16 [INFO] [stderr] | [INFO] [stderr] 25 | let json = grammar! { [INFO] [stderr] | ________________^ [INFO] [stderr] 26 | | parse: JsonValue = "=" [INFO] [stderr] 27 | | [INFO] [stderr] 28 | | num: f32 = ::recognize_float => { result.parse::().unwrap() } [INFO] [stderr] ... | [INFO] [stderr] 51 | | | boolean => { JsonValue::Boolean(result) } [INFO] [stderr] 52 | | }; [INFO] [stderr] | |_____^ invalid suffix `usize` [INFO] [stderr] | [INFO] [stderr] = note: `usize` is *temporarily* accepted on tuple index fields as it was incorrectly accepted on stable for a few releases [INFO] [stderr] = help: on proc macros, you'll want to use `syn::Index::from` or `proc_macro::Literal::*_unsuffixed` for code that will desugar to tuple field access [INFO] [stderr] = note: for more context, see https://github.com/rust-lang/rust/issues/60210 [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> tests/basic.rs:39:22 [INFO] [stderr] | [INFO] [stderr] 39 | let arithmetic = grammar! { [INFO] [stderr] | ______________________^ [INFO] [stderr] 40 | | parse: i64 = "=" [INFO] [stderr] 41 | | [INFO] [stderr] 42 | | expr: i64 = "+" => { l + r } [INFO] [stderr] ... | [INFO] [stderr] 51 | | | "(" ")" [INFO] [stderr] 52 | | }; [INFO] [stderr] | |_____^ invalid suffix `usize` [INFO] [stderr] | [INFO] [stderr] = note: `usize` is *temporarily* accepted on tuple index fields as it was incorrectly accepted on stable for a few releases [INFO] [stderr] = help: on proc macros, you'll want to use `syn::Index::from` or `proc_macro::Literal::*_unsuffixed` for code that will desugar to tuple field access [INFO] [stderr] = note: for more context, see https://github.com/rust-lang/rust/issues/60210 [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.83s [INFO] running `"docker" "inspect" "a9c8e4de10d7d7229937e34466ac9ee5aff188ab2662f13e16410bea29ca5b63"` [INFO] running `"docker" "rm" "-f" "a9c8e4de10d7d7229937e34466ac9ee5aff188ab2662f13e16410bea29ca5b63"` [INFO] [stdout] a9c8e4de10d7d7229937e34466ac9ee5aff188ab2662f13e16410bea29ca5b63