pkg/build: extract bazel build errors

We currently manually call extractRootCause in few selected places
to denote kernel build errors that we want to report to developers.
The rest are considered infra errors that we don't report.
This does not work well. We are missing fuchsia and gvisor build errors.
Treat all external command exection failures as kernel build errors instead.
Let's see how this works in practice.
Also add bazel-specfic error patterns and tests.
5 files changed
tree: 01efde3d54f1261007510e6662045f07f1621cd2
  1. .clang-format
  2. .gitignore
  3. .golangci.yml
  4. .gometalinter.json
  5. .travis.yml
  6. AUTHORS
  7. CODE_OF_CONDUCT.md
  8. CONTRIBUTORS
  9. Godeps/
  10. LICENSE
  11. Makefile
  12. README.md
  13. dashboard/
  14. docs/
  15. executor/
  16. fuzz.yaml
  17. pkg/
  18. prog/
  19. sys/
  20. syz-ci/
  21. syz-fuzzer/
  22. syz-hub/
  23. syz-manager/
  24. tools/
  25. vendor/
  26. vm/
README.md

syzkaller - kernel fuzzer

Build Status Go Report Card Coverage Status GoDoc License

syzkaller is an unsupervised coverage-guided kernel fuzzer.
Supported OSes: Akaros, FreeBSD, Fuchsia, gVisor, Linux, NetBSD, OpenBSD, Windows.

Mailing list: syzkaller@googlegroups.com (join on web or by email).

Found bugs: Akaros, Darwin/XNU, FreeBSD, Linux, NetBSD, OpenBSD, Windows.

Documentation

Initially, syzkaller was developed with Linux kernel fuzzing in mind, but now it's being extended to support other OS kernels as well. Most of the documentation at this moment is related to the Linux kernel. For other OS kernels check: Akaros, Darwin/XNU, FreeBSD, Fuchsia, NetBSD, OpenBSD, Windows, gVisor.

External Articles

Disclaimer

This is not an official Google product.