[INFO] crate lark-parser 0.1.0 is already in cache [INFO] checking lark-parser-0.1.0 against master#45d050cde277b22a755847338f2acc2c7b834141 for pr-71393 [INFO] extracting crate lark-parser 0.1.0 into /workspace/builds/worker-6/source [INFO] validating manifest of crates.io crate lark-parser 0.1.0 on toolchain 45d050cde277b22a755847338f2acc2c7b834141 [INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate lark-parser 0.1.0 [INFO] finished tweaking crates.io crate lark-parser 0.1.0 [INFO] tweaked toml for crates.io crate lark-parser 0.1.0 written to /workspace/builds/worker-6/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6/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" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+45d050cde277b22a755847338f2acc2c7b834141" "check" "--frozen" "--all" "--all-targets"` [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] b1b7a7e5f7b92536e9dbc17e7bad790f431492858bcc8d247cb266922b5052a0 [INFO] running `"docker" "start" "-a" "b1b7a7e5f7b92536e9dbc17e7bad790f431492858bcc8d247cb266922b5052a0"` [INFO] [stderr] Checking unindent v0.1.5 [INFO] [stderr] Compiling num-integer v0.1.42 [INFO] [stderr] Checking itertools v0.8.2 [INFO] [stderr] Checking atty v0.2.14 [INFO] [stderr] Checking time v0.1.43 [INFO] [stderr] Checking render-tree v0.1.1 [INFO] [stderr] Checking salsa v0.9.2 [INFO] [stderr] Checking env_logger v0.6.2 [INFO] [stderr] Checking language-reporting v0.3.1 [INFO] [stderr] Checking chrono v0.4.11 [INFO] [stderr] Checking lark-span v0.1.0 [INFO] [stderr] Checking lark-error v0.1.0 [INFO] [stderr] Checking pretty_env_logger v0.3.1 [INFO] [stderr] Checking lark-entity v0.1.0 [INFO] [stderr] Checking lark-ty v0.1.0 [INFO] [stderr] Checking lark-hir v0.1.0 [INFO] [stderr] Checking lark-parser v0.1.0 (/opt/rustwide/workdir) [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/delimited.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/delimited.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/guard.rs:12:10 [INFO] [stderr] | [INFO] [stderr] 12 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/list.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/list.rs:50:10 [INFO] [stderr] | [INFO] [stderr] 50 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/matched.rs:11:10 [INFO] [stderr] | [INFO] [stderr] 11 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/skip_newline.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/guard.rs:12:10 [INFO] [stderr] | [INFO] [stderr] 12 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/list.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/list.rs:50:10 [INFO] [stderr] | [INFO] [stderr] 50 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/matched.rs:11:10 [INFO] [stderr] | [INFO] [stderr] 11 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: suffixes on a tuple index are invalid [INFO] [stderr] --> src/syntax/skip_newline.rs:8:10 [INFO] [stderr] | [INFO] [stderr] 8 | #[derive(DebugWith)] [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: see issue #60210 for more information [INFO] [stderr] = note: this warning originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: 6 warnings emitted [INFO] [stderr] [INFO] [stderr] warning: 6 warnings emitted [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 14.51s [INFO] running `"docker" "inspect" "b1b7a7e5f7b92536e9dbc17e7bad790f431492858bcc8d247cb266922b5052a0"` [INFO] running `"docker" "rm" "-f" "b1b7a7e5f7b92536e9dbc17e7bad790f431492858bcc8d247cb266922b5052a0"` [INFO] [stdout] b1b7a7e5f7b92536e9dbc17e7bad790f431492858bcc8d247cb266922b5052a0