[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] testing tkclimb/jack-lang against 1.55.0 for beta-1.56-1
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Ftkclimb%2Fjack-lang" "/workspace/builds/worker-116/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-116/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/tkclimb/jack-lang on toolchain 1.55.0
[INFO] running `Command { std: "/workspace/cargo-home/bin/cargo" "+1.55.0" "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-116/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" "+1.55.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-116/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-116/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:a89201d6b5b9fd45c15d5952ece0a0129e7e80cb26ec023fd59cf09bc26f1604" "/opt/rustwide/cargo-home/bin/cargo" "+1.55.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 73625ca5b2ff41324e85ca647828efcd6251f4ec4f943eb4fcbb43a51d2213dd
[INFO] running `Command { std: "docker" "start" "-a" "73625ca5b2ff41324e85ca647828efcd6251f4ec4f943eb4fcbb43a51d2213dd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "73625ca5b2ff41324e85ca647828efcd6251f4ec4f943eb4fcbb43a51d2213dd", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "73625ca5b2ff41324e85ca647828efcd6251f4ec4f943eb4fcbb43a51d2213dd", kill_on_drop: false }`
[INFO] [stdout] 73625ca5b2ff41324e85ca647828efcd6251f4ec4f943eb4fcbb43a51d2213dd
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-116/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-116/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=warn" "-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:a89201d6b5b9fd45c15d5952ece0a0129e7e80cb26ec023fd59cf09bc26f1604" "/opt/rustwide/cargo-home/bin/cargo" "+1.55.0" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 6bb993329eb333a0b26df112737797c53470f3938714b2e5aedad3781c0cbb75
[INFO] running `Command { std: "docker" "start" "-a" "6bb993329eb333a0b26df112737797c53470f3938714b2e5aedad3781c0cbb75", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[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 syn v1.0.42
[INFO] [stderr]    Compiling serde_derive v1.0.116
[INFO] [stderr]    Compiling serde v1.0.116
[INFO] [stderr]    Compiling string_cache_shared v0.3.0
[INFO] [stderr]    Compiling byteorder v1.3.4
[INFO] [stderr]    Compiling regex v0.2.11
[INFO] [stderr]    Compiling log v0.4.11
[INFO] [stderr]    Compiling ucd-util v0.1.8
[INFO] [stderr]    Compiling utf8-ranges v1.0.4
[INFO] [stderr]    Compiling regex-syntax v0.6.18
[INFO] [stderr]    Compiling cc v1.0.60
[INFO] [stderr]    Compiling term v0.4.6
[INFO] [stderr]    Compiling ordermap v0.3.5
[INFO] [stderr]    Compiling fixedbitset v0.1.9
[INFO] [stderr]    Compiling new_debug_unreachable v1.0.4
[INFO] [stderr]    Compiling bit-vec v0.6.2
[INFO] [stderr]    Compiling strsim v0.9.3
[INFO] [stderr]    Compiling precomputed-hash v0.1.1
[INFO] [stderr]    Compiling either v1.6.1
[INFO] [stderr]    Compiling lalrpop-util v0.16.3
[INFO] [stderr]    Compiling diff v0.1.12
[INFO] [stderr]    Compiling unicode-width v0.1.8
[INFO] [stderr]    Compiling vec_map v0.8.2
[INFO] [stderr]    Compiling phf_shared v0.7.24
[INFO] [stderr]    Compiling thread_local v0.3.6
[INFO] [stderr]    Compiling semver v0.9.0
[INFO] [stderr]    Compiling aho-corasick v0.7.13
[INFO] [stderr]    Compiling aho-corasick v0.6.10
[INFO] [stderr]    Compiling regex-syntax v0.5.6
[INFO] [stderr]    Compiling textwrap v0.11.0
[INFO] [stderr]    Compiling itertools v0.8.2
[INFO] [stderr]    Compiling petgraph v0.4.13
[INFO] [stderr]    Compiling bit-set v0.5.2
[INFO] [stderr]    Compiling ascii-canvas v1.0.0
[INFO] [stderr]    Compiling ena v0.11.0
[INFO] [stderr]    Compiling quote v1.0.7
[INFO] [stderr]    Compiling generic-array v0.12.3
[INFO] [stderr]    Compiling rand_os v0.1.3
[INFO] [stderr]    Compiling atty v0.2.14
[INFO] [stderr]    Compiling clap v2.33.3
[INFO] [stderr]    Compiling rand v0.6.5
[INFO] [stderr]    Compiling block-buffer v0.7.3
[INFO] [stderr]    Compiling digest v0.8.1
[INFO] [stderr]    Compiling sha2 v0.8.2
[INFO] [stderr]    Compiling phf_generator v0.7.24
[INFO] [stderr]    Compiling regex v1.3.9
[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 (/opt/rustwide/workdir)
[INFO] [stderr] error: failed to run custom build command for `jack-lang v0.1.0 (/opt/rustwide/workdir)`
[INFO] [stderr] 
[INFO] [stderr] Caused by:
[INFO] [stderr]   process didn't exit successfully: `/opt/rustwide/target/debug/build/jack-lang-a8c280d59ed9a465/build-script-build` (exit status: 1)
[INFO] [stderr]   --- stdout
[INFO] [stderr]   processing file `/opt/rustwide/workdir/src/grammar.lalrpop`
[INFO] [stderr]   /opt/rustwide/workdir/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]     /opt/rustwide/workdir/src/grammar.lalrpop:43:11: 43:24, which would consume
[INFO] [stderr]     the top 1 token(s) from the stack and produce a `(<Statement>)+`. This might
[INFO] [stderr]     then yield 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]   /opt/rustwide/workdir/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]     /opt/rustwide/workdir/src/grammar.lalrpop:43:11: 43:24, which would consume
[INFO] [stderr]     the top 2 token(s) from the stack and produce a `(<Statement>)+`. This might
[INFO] [stderr]     then yield 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]   /opt/rustwide/workdir/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]     /opt/rustwide/workdir/src/grammar.lalrpop:43:11: 43:24, which would consume
[INFO] [stderr]     the top 1 token(s) from the stack and produce a `(<Statement>)+`. This might
[INFO] [stderr]     then yield 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] running `Command { std: "docker" "inspect" "6bb993329eb333a0b26df112737797c53470f3938714b2e5aedad3781c0cbb75", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "6bb993329eb333a0b26df112737797c53470f3938714b2e5aedad3781c0cbb75", kill_on_drop: false }`
[INFO] [stdout] 6bb993329eb333a0b26df112737797c53470f3938714b2e5aedad3781c0cbb75