Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).


More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.
depot_tools:
  https://crrev.com/9f531298e1a38ccd52b4bd8c47593ccc8f514e04 gclient eval: Get rid of global_scope, local_scope and functions other than Var. (ehmaldonado@chromium.org)
  https://crrev.com/869a2857a4f3acc08fdec6182ecec5b73593be3b Revert "Add debugging info when gclient deletes an old DEPS entry." (thestig@chromium.org)
  https://crrev.com/c621b21ad4bfce59924ffc0116eff58bcd4b8bc0 gclient sync: Add support to apply gerrit refs. (ehmaldonado@chromium.org)
  https://crrev.com/5025893cb6061b8a219750155cccd67b55079311 [presubmit_support] Prevent depot_tools' virtualenv from leaking into other repos. (iannucci@chromium.org)
  https://crrev.com/e8703543e3930885d28e561bcf2ab9638b7eeb45 Trigger recipe roll to pick up 5025893cb6061b8a219750155cccd67b55079311. (iannucci@chromium.org)


TBR=borenet@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ic483d688277d71642b6f544113aee0d4cb35287d
Reviewed-on: https://skia-review.googlesource.com/116001
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
2 files changed
tree: 783d9257871711dd54974ade6c692ce5b28df85e
  1. android_compile/
  2. android_ingest/
  3. android_stats/
  4. ap/
  5. appengine_scripts/
  6. autoroll/
  7. bash/
  8. blamer/
  9. chromeextensions/
  10. cmd/
  11. comments/
  12. common/
  13. contest/
  14. coverage/
  15. cq_watcher/
  16. ct/
  17. ct_pixel_diff/
  18. datahopper/
  19. debugger/
  20. doc/
  21. ds/
  22. fiddle/
  23. flakiness/
  24. fuzzer/
  25. get_service_account/
  26. git_cookie_authdaemon/
  27. go/
  28. golden/
  29. grafana/
  30. infra/
  31. jsdoc/
  32. leasing/
  33. logmetrics/
  34. misc/
  35. monitoring/
  36. pdfium/
  37. perdiff/
  38. perf/
  39. power/
  40. predict/
  41. prober/
  42. prometheus/
  43. proxy/
  44. pulld/
  45. push/
  46. res/
  47. scripts/
  48. skfe/
  49. skolo/
  50. status/
  51. statusv2/
  52. swarming_logger/
  53. task_scheduler/
  54. tools/
  55. tracedb/
  56. webtools/
  57. .gitattributes
  58. .gitignore
  59. codereview.settings
  60. DATASTORE.md
  61. DEPS
  62. launch.md
  63. LICENSE
  64. Makefile
  65. PRESUBMIT.py
  66. README.md
  67. run_unittests
  68. run_unittests.go
  69. STYLEGUIDE.md
  70. whitespace.txt
README.md

Skia-Buildbot Repository

This repo contains infrastructure code for Skia.

Getting the Source Code

The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot. Although it is possible to check out this repository directly with git clone or using gclient fetch, it is preferred to use go get so that the code is arranged correctly for Go. If this is your first time working on Go code, read about the GOPATH environment variable. Make sure that $GOPATH/bin comes before /usr/bin in your PATH. If you have GOPATH set, run:

$ go get -u -t go.skia.org/infra/...

This fetches the repository into your $GOPATH directory along with all the Go dependencies. Note: go.skia.org is a custom import path and will only work if used like the examples here.

Install Node.js (not as root) and add the bin dir to your path. Optionally run npm install npm -g, as suggested by the npm getting started doc.

Install other dependencies:

$ sudo apt-get install python-django
$ go get -u github.com/kisielk/errcheck \
  golang.org/x/tools/cmd/goimports \
  go.chromium.org/luci/client/cmd/isolate
$ npm install -g polylint bower

Build from GOPATH:

$ cd $GOPATH/src/go.skia.org/infra/
$ make all

Generated Code

Some code is generated using go generate with external binaries. First, install the version of protoc referenced in the asset creation script and ensure it is on your PATH before other versions of protoc.

Install the necessary go packages:

$ go get -u \
  github.com/golang/protobuf/protoc-gen-go \
  golang.org/x/tools/cmd/stringer \
  google.golang.org/grpc

To generate code run in this directory:

$ go generate ./...

Database Setup for Testing

Tests which use the database package's testutils require you to have a MySQL instance running with a database named “sk_testing” and users called “readwrite” and “test_root” with appropriate permissions for sk_testing. The ‘setup_test_db’ script in ‘go/database’ is included for convenience in setting up this test database and user.

Go tests require a local installation of MySQL. For a Debian based distro:

$ sudo apt-get install mysql-client mysql-server

Leave the root password blank.

Then, to set up local versions of the production databases:

$ cd $GOPATH/src/go.skia.org/infra/go/database
$ ./setup_test_db

Running unit tests

Install Cloud SDK.

The installed python-django version must be >= 1.7. Run the following to update:

$ sudo pip install Django --upgrade

Use this command to run the presubmit tests:

$ ./run_unittests --small