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/e9e89e3aa538298f77e98da01bc36416118e9e88 Improve error message for missing gerrit credentials in git-cl. (whesse@google.com)
  https://crrev.com/da4dbf85f95051345f147cfe69d909d85e81a429 autoninja: limit j value for mac (tikuta@chromium.org)
recipe_engine:
  https://crrev.com/ae3604f2d2ae0291ecdc690672cc173e06a965ba [proto_support] Handle unicode filesystem walks. (iannucci@chromium.org)


TBR=borenet@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Iea03d3024ba50c73954d9a43b7b1f4beef917d55
Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/196802
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
2 files changed
tree: a7ca323ee2374c8c8dfea677a04a765e114da8ce
  1. am/
  2. android_compile/
  3. android_ingest/
  4. android_stats/
  5. appengine_scripts/
  6. autoroll/
  7. bash/
  8. blamer/
  9. chromeextensions/
  10. cmd/
  11. comments/
  12. common-sk/
  13. contestk/
  14. cq_watcher/
  15. ct/
  16. ct_pixel_diff/
  17. datahopper/
  18. debugger/
  19. debugger-assets/
  20. docker/
  21. docserverk/
  22. ds/
  23. fiddlek/
  24. firestore/
  25. fuzzer/
  26. get_service_account/
  27. git_cookie_authdaemon/
  28. gitsync/
  29. go/
  30. gold-client/
  31. golden/
  32. grafana/
  33. html-template-minifier/
  34. infra/
  35. infra-sk/
  36. jsdoc/
  37. jsfiddle/
  38. kube/
  39. leasing/
  40. license/
  41. logmetrics/
  42. make/
  43. monitoring/
  44. named-fiddles/
  45. notifier/
  46. pdfium/
  47. perdiff/
  48. perf/
  49. periodic-trigger/
  50. power/
  51. prober/
  52. proberk/
  53. prometheus/
  54. promk/
  55. proxy/
  56. pulld/
  57. push/
  58. res/
  59. scripts/
  60. sheriff_emails/
  61. skfe/
  62. skolo/
  63. skottie/
  64. status/
  65. task_driver/
  66. task_scheduler/
  67. tools/
  68. tracedb/
  69. webtools/
  70. .gitattributes
  71. .gitignore
  72. build_infra_prod.sh
  73. codereview.settings
  74. DATASTORE.md
  75. DEPS
  76. launch.md
  77. LICENSE
  78. Makefile
  79. PRESUBMIT.py
  80. PRIVACY_POLICY.md
  81. README.md
  82. run_unittests
  83. run_unittests.go
  84. STYLEGUIDE.md
  85. 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