[INFO] cloning repository https://github.com/tkclimb/jack-lang
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/tkclimb/jack-lang" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Ftkclimb%2Fjack-lang", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Ftkclimb%2Fjack-lang'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] 506b42bec1e592b2c0838e8929a7d797a1c18d44
[INFO] checking tkclimb/jack-lang against try#a7a572ce3edd6d476191fbfe92c9c1986e009b34 for pr-87190-3
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Ftkclimb%2Fjack-lang" "/workspace/builds/worker-1/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-1/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/tkclimb/jack-lang on toolchain a7a572ce3edd6d476191fbfe92c9c1986e009b34
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking git repo https://github.com/tkclimb/jack-lang
[INFO] finished tweaking git repo https://github.com/tkclimb/jack-lang
[INFO] tweaked toml for git repo https://github.com/tkclimb/jack-lang written to /workspace/builds/worker-1/source/Cargo.toml
[INFO] crate git repo https://github.com/tkclimb/jack-lang already has a lockfile, it will not be regenerated
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded llvm-sys v60.6.0
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/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:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] e03d71db42937fc964c102cd4eb7f14b3d2cca78ff3a95e6f46821f99d724122
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "e03d71db42937fc964c102cd4eb7f14b3d2cca78ff3a95e6f46821f99d724122", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "e03d71db42937fc964c102cd4eb7f14b3d2cca78ff3a95e6f46821f99d724122", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e03d71db42937fc964c102cd4eb7f14b3d2cca78ff3a95e6f46821f99d724122", kill_on_drop: false }`
[INFO] [stdout] e03d71db42937fc964c102cd4eb7f14b3d2cca78ff3a95e6f46821f99d724122
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:34b6a614d2c27851fe6cbf88fbd1137609cefab8b10d0615aaeb6fd47975d74e" "/opt/rustwide/cargo-home/bin/cargo" "+a7a572ce3edd6d476191fbfe92c9c1986e009b34" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] bb5728cd8d64249fb123f218c7f95c50baebb436f0aff450fd3322b1a1077164
[INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
[INFO] running `Command { std: "docker" "start" "-a" "bb5728cd8d64249fb123f218c7f95c50baebb436f0aff450fd3322b1a1077164", kill_on_drop: false }`
[INFO] [stderr] Copying to /tmp/fixit
[INFO] [stderr] Running `cargo fix --edition`
[INFO] [stderr] note: Switching to Edition 2021 will enable the use of the version 2 feature resolver in Cargo.
[INFO] [stderr] This may cause some dependencies to be built with fewer features enabled than previously.
[INFO] [stderr] More information about the resolver changes may be found at https://doc.rust-lang.org/nightly/edition-guide/rust-2021/default-cargo-resolver.html
[INFO] [stderr] When building the following dependencies, the given features will no longer be used:
[INFO] [stderr] 
[INFO] [stderr]   memchr v2.3.3: use_std
[INFO] [stderr] 
[INFO] [stderr]    Compiling rand_core v0.4.2
[INFO] [stderr]    Compiling libc v0.2.77
[INFO] [stderr]    Compiling proc-macro2 v1.0.23
[INFO] [stderr]    Compiling typenum v1.12.0
[INFO] [stderr]    Compiling siphasher v0.2.3
[INFO] [stderr]    Compiling syn v1.0.42
[INFO] [stderr]    Compiling serde_derive v1.0.116
[INFO] [stderr]    Compiling string_cache_shared v0.3.0
[INFO] [stderr]    Compiling serde v1.0.116
[INFO] [stderr]    Compiling byteorder v1.3.4
[INFO] [stderr]    Compiling ucd-util v0.1.8
[INFO] [stderr]    Compiling utf8-ranges v1.0.4
[INFO] [stderr]    Compiling either v1.6.1
[INFO] [stderr]    Compiling ordermap v0.3.5
[INFO] [stderr]    Compiling bit-vec v0.6.2
[INFO] [stderr]    Compiling fixedbitset v0.1.9
[INFO] [stderr]    Compiling new_debug_unreachable v1.0.4
[INFO] [stderr]    Compiling term v0.4.6
[INFO] [stderr]    Compiling cc v1.0.60
[INFO] [stderr]    Compiling precomputed-hash v0.1.1
[INFO] [stderr]    Compiling bitflags v1.2.1
[INFO] [stderr]    Compiling diff v0.1.12
[INFO] [stderr]    Compiling lalrpop-util v0.16.3
[INFO] [stderr]    Compiling thread_local v0.3.6
[INFO] [stderr]    Compiling rand_core v0.3.1
[INFO] [stderr]    Compiling rand_jitter v0.1.4
[INFO] [stderr]    Compiling phf_shared v0.7.24
[INFO] [stderr]    Compiling itertools v0.8.2
[INFO] [stderr]    Compiling regex-syntax v0.5.6
[INFO] [stderr]    Compiling bit-set v0.5.2
[INFO] [stderr]     Checking textwrap v0.11.0
[INFO] [stderr]    Compiling memchr v2.3.3
[INFO] [stderr]    Compiling log v0.4.11
[INFO] [stderr]    Compiling rand_hc v0.1.0
[INFO] [stderr]    Compiling rand_xorshift v0.1.1
[INFO] [stderr]    Compiling rand_isaac v0.1.1
[INFO] [stderr]    Compiling ascii-canvas v1.0.0
[INFO] [stderr]    Compiling petgraph v0.4.13
[INFO] [stderr]     Checking aho-corasick v0.6.10
[INFO] [stderr]    Compiling rand_chacha v0.1.1
[INFO] [stderr]    Compiling rand_pcg v0.1.2
[INFO] [stderr]    Compiling ena v0.11.0
[INFO] [stderr]    Compiling aho-corasick v0.7.13
[INFO] [stderr]     Checking regex v0.2.11
[INFO] [stderr]     Checking atty v0.2.14
[INFO] [stderr]     Checking clap v2.33.3
[INFO] [stderr]    Compiling rand_os v0.1.3
[INFO] [stderr]    Compiling quote v1.0.7
[INFO] [stderr]    Compiling rand v0.6.5
[INFO] [stderr]    Compiling generic-array v0.12.3
[INFO] [stderr]    Compiling regex v1.3.9
[INFO] [stderr]    Compiling digest v0.8.1
[INFO] [stderr]    Compiling block-buffer v0.7.3
[INFO] [stderr]    Compiling sha2 v0.8.2
[INFO] [stderr]    Compiling phf_generator v0.7.24
[INFO] [stderr]    Compiling string_cache_codegen v0.4.4
[INFO] [stderr]    Compiling string_cache v0.7.5
[INFO] [stderr]    Compiling llvm-sys v60.6.0
[INFO] [stderr]    Compiling docopt v1.1.0
[INFO] [stderr]    Compiling lalrpop v0.16.3
[INFO] [stderr]    Compiling jack-lang v0.1.0 (/tmp/fixit)
[INFO] [stderr]    Migrating build.rs from 2018 edition to 2021
[INFO] [stderr] error: failed to run custom build command for `jack-lang v0.1.0 (/tmp/fixit)`
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `/opt/rustwide/target/debug/build/jack-lang-abbe71184a9d67b1/build-script-build` (exit status: 1)
[INFO] [stderr]   --- stdout
[INFO] [stderr]   processing file `/tmp/fixit/src/grammar.lalrpop`
[INFO] [stderr]   /tmp/fixit/src/grammar.lalrpop:43:11: 43:24: Local ambiguity detected
[INFO] [stderr] 
[INFO] [stderr]     The problem arises after having observed the following symbols in the input:
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" Statement
[INFO] [stderr]     At that point, if the next token is a `"}"`, then the parser can proceed in
[INFO] [stderr]     two different ways.
[INFO] [stderr] 
[INFO] [stderr]     First, the parser could execute the production at
[INFO] [stderr]     /tmp/fixit/src/grammar.lalrpop:43:11: 43:24, which would consume the top 1
[INFO] [stderr]     token(s) from the stack and produce a `(<Statement>)+`. This might then yield
[INFO] [stderr]     a parse tree like
[INFO] [stderr]       "{" Statement        ╷ "}"
[INFO] [stderr]       │   └─(<Statement>)+─┘   │
[INFO] [stderr]       └─Stmtblock──────────────┘
[INFO] [stderr] 
[INFO] [stderr]     Alternatively, the parser could shift the `"}"` token and later use it to
[INFO] [stderr]     construct a `Stmtblock`. This might then yield a parse tree like
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" Statement "}"
[INFO] [stderr]       │                                └─Stmtblock─────┤
[INFO] [stderr]       └─FnDecl─────────────────────────────────────────┘
[INFO] [stderr] 
[INFO] [stderr]     See the LALRPOP manual for advice on making your grammar LR(1).
[INFO] [stderr] 
[INFO] [stderr]   /tmp/fixit/src/grammar.lalrpop:43:11: 43:24: Local ambiguity detected
[INFO] [stderr] 
[INFO] [stderr]     The problem arises after having observed the following symbols in the input:
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" (<Statement>)+ Statement
[INFO] [stderr]     At that point, if the next token is a `"}"`, then the parser can proceed in
[INFO] [stderr]     two different ways.
[INFO] [stderr] 
[INFO] [stderr]     First, the parser could execute the production at
[INFO] [stderr]     /tmp/fixit/src/grammar.lalrpop:43:11: 43:24, which would consume the top 2
[INFO] [stderr]     token(s) from the stack and produce a `(<Statement>)+`. This might then yield
[INFO] [stderr]     a parse tree like
[INFO] [stderr]       "{" (<Statement>)+ Statement "}"
[INFO] [stderr]       │   └─(<Statement>)+───────┘   │
[INFO] [stderr]       └─Stmtblock────────────────────┘
[INFO] [stderr] 
[INFO] [stderr]     Alternatively, the parser could shift the `"}"` token and later use it to
[INFO] [stderr]     construct a `Stmtblock`. This might then yield a parse tree like
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" (<Statement>)+ Statement "}"
[INFO] [stderr]       │                                └─Stmtblock────────────────────┤
[INFO] [stderr]       └─FnDecl────────────────────────────────────────────────────────┘
[INFO] [stderr] 
[INFO] [stderr]     See the LALRPOP manual for advice on making your grammar LR(1).
[INFO] [stderr] 
[INFO] [stderr]   /tmp/fixit/src/grammar.lalrpop:43:11: 43:24: Local ambiguity detected
[INFO] [stderr] 
[INFO] [stderr]     The problem arises after having observed the following symbols in the input:
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" Statement
[INFO] [stderr]     At that point, if the next token is a `"}"`, then the parser can proceed in
[INFO] [stderr]     two different ways.
[INFO] [stderr] 
[INFO] [stderr]     First, the parser could execute the production at
[INFO] [stderr]     /tmp/fixit/src/grammar.lalrpop:43:11: 43:24, which would consume the top 1
[INFO] [stderr]     token(s) from the stack and produce a `(<Statement>)+`. This might then yield
[INFO] [stderr]     a parse tree like
[INFO] [stderr]       "{" Statement        ╷ "}"
[INFO] [stderr]       │   └─(<Statement>)+─┘   │
[INFO] [stderr]       └─Stmtblock──────────────┘
[INFO] [stderr] 
[INFO] [stderr]     Alternatively, the parser could shift the `"}"` token and later use it to
[INFO] [stderr]     construct a `Stmtblock`. This might then yield a parse tree like
[INFO] [stderr]       "fn" RawId FnDeclArgs "->" RawId "{" Statement "}"
[INFO] [stderr]       │                                └─Stmtblock─────┤
[INFO] [stderr]       └─FnDecl─────────────────────────────────────────┘
[INFO] [stderr] 
[INFO] [stderr]     See the LALRPOP manual for advice on making your grammar LR(1).
[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" "bb5728cd8d64249fb123f218c7f95c50baebb436f0aff450fd3322b1a1077164", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "bb5728cd8d64249fb123f218c7f95c50baebb436f0aff450fd3322b1a1077164", kill_on_drop: false }`
[INFO] [stdout] bb5728cd8d64249fb123f218c7f95c50baebb436f0aff450fd3322b1a1077164