setup
checks.aarch64-linux.ast-grep
· build #766
· raw
1this derivation will be built:2 /nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv3error: build of '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv' on 'grpc://farm.numtide.com:50051?connect-timeout=20&system=aarch64-linux&token-file=/run/nix-farm-client/farm-token' failed: Cannot build '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv'.4 Reason: builder failed with exit code 1.5 Output paths:6 /nix/store/7ghag4ad96q5nkxg0iw6xl9z33sk3pr9-iets-ast-grep7 Last 25 log lines:8 > │9 > 184 │ ╭ /// the path resolution ended at, and its place in the (virtual) store, `None`10 > 185 │ │ ╭ /// for one the real file system answers. [`resolve_links`] runs under a store11 > │ ╰────────────'12 > 186 │ │ ╭ /// path this evaluation copied from a local tree, and in a pure evaluation13 > │ ╰──────────'14 > 187 │ │ ╭ /// under the project: there the kernel would follow a link out of the allow15 > │ ╰────────'16 > 188 │ │ ╭ /// list, which is judged on the text of the path. A fetched input's spool17 > │ ╰──────'18 > 189 │ │ ╭ /// resolves a member's links inside the entry itself, and elsewhere the19 > │ ╰────'20 > 190 │ │ ╭ /// kernel resolves as the accessor would, so the walk is skipped and this21 > │ ╰──'22 > 191 │ ╭ │ /// costs the one lookup the reader needed anyway.23 > │ │ ╰'24 > 192 │ │ ╭ pub fn located(25 > │ ╰────────────────^26 > · │27 > 217 │ │ }28 > │ ╰───────────────'29 >30 > Error: 3 error(s) found in code.31 > Help: Scan succeeded and found error level diagnostics in the codebase.32 >33 For full logs, run:34 nix log /nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv35error: Cannot build '/nix/store/5wcnsbxndhnjl9vaimixzn8gliw1mxf2-iets-ast-grep.drv'.36 Reason: builder failed with exit code 1.37 Output paths:38 /nix/store/7ghag4ad96q5nkxg0iw6xl9z33sk3pr9-iets-ast-grep