[engine] Add more benchmarks in testdata/bench/

They are all simple. They will provide information for follow up
changes.

What is most interesting is the amount of memory used. In particular,
BenchmarkPrint_Git versus BenchmarkPrint_Raw shows that the git querying
is causing a significant amount of overhead.

Update common test code from *testing.T to testing.TB.

Update scritps/tests.sh to work when called from anywhere, and run
benchmarks.

Test only change.

Change-Id: I1735f6ee29d37b6a68566ffaab339d6461af4d92
Reviewed-on: https://fuchsia-review.googlesource.com/c/shac-project/shac/+/859536
Reviewed-by: Oliver Newman <olivernewman@google.com>
Fuchsia-Auto-Submit: Marc-Antoine Ruel <maruel@google.com>
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
14 files changed
tree: c37f5a003dc8cb7782afabee7b8d2c1b5fd3a993
  1. .github/
  2. doc/
  3. internal/
  4. scripts/
  5. .gitignore
  6. AUTHORS
  7. check_doc.star
  8. codecov.yml
  9. CONTRIBUTING.md
  10. go.mod
  11. go.star
  12. go.sum
  13. LICENSE
  14. licenses.star
  15. main.go
  16. OWNERS
  17. PATENTS
  18. README.md
  19. shac.star
  20. shac.textproto
README.md

shac

Scalable Hermetic Analysis and Checks.

Usage

go install go.fuchsia.dev/shac-project/shac@latest
shac check
shac doc shac.star | less

Documentation

Contributing

⚠ The source of truth is at https://fuchsia.googlesource.com/shac-project/shac.git and uses Gerrit for code review.

See CONTRIBUTING.md to submit changes.