Starting local Bazel server and connecting to it...
Loading: 
Loading: 1 packages loaded
Analyzing: target //runsc:runsc (2 packages loaded, 0 targets configured)
Analyzing: target //runsc:runsc (64 packages loaded, 8367 targets configured)
Analyzing: target //runsc:runsc (369 packages loaded, 15161 targets configured)
DEBUG: /syzkaller/.cache/bazel/_bazel_root/cf34e0740923b98f815a07e89b50b289/external/io_bazel_rules_go/extras/embed_data.bzl:43:10: Embedding is now better handled by using rules_go's built-in embedding functionality (https://github.com/bazelbuild/rules_go/blob/master/docs/go/core/rules.md#go_library-embedsrcs). The `go_embed_data` rule is deprecated and will be removed in rules_go version 0.39.
INFO: Analyzed target //runsc:runsc (373 packages loaded, 17909 targets configured).
INFO: Found 1 target...
[3 / 78] [Prepa] BazelWorkspaceStatusAction stable-status.txt
ERROR: /syzkaller/managers/ci-gvisor-arm64-ptrace-1/kernel/vdso/BUILD:13:8: Executing genrule //vdso:vdso failed: (Exit 127): bash failed: error executing command 
  (cd /syzkaller/.cache/bazel/_bazel_root/cf34e0740923b98f815a07e89b50b289/sandbox/linux-sandbox/1/execroot/__main__ && \
  exec env - \
    PATH=/usr/local/go/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; /usr/bin/x86_64-linux-gnu-gcc  -I. -O2 -std=c++11 -fPIC -fno-sanitize=all -fno-stack-protector -fuse-ld=gold -shared -nostdlib -Wl,-soname=linux-vdso.so.1 -Wl,--hash-style=sysv -Wl,--no-undefined -Wl,-Bsymbolic -Wl,-z,max-page-size=4096 -Wl,-z,common-page-size=4096 -Wl,-Tvdso/vdso_amd64.lds -o bazel-out/k8-fastbuild-ST-027b4cb11759/bin/vdso/vdso.so vdso/vdso.cc vdso/vdso_time.cc')
# Configuration: 30e3ca005772fd1c2e2065b488b132457dd90ccb47117f721f1e4e8fa6f3b6e7
# Execution platform: @local_config_platform//:host

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: line 1: /usr/bin/x86_64-linux-gnu-gcc: No such file or directory
Target //runsc:runsc failed to build
INFO: Elapsed time: 7.281s, Critical Path: 0.06s
INFO: 3 processes: 3 internal.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully