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/98681d113f3ebb6e0e76855cc884fd599ea8549f Remove obsolete destination-branch-check flag (machenbach@chromium.org)


TBR=borenet@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I57d119444ff4205ba00986e3d59bb51f88f87ff1
Reviewed-on: https://skia-review.googlesource.com/23901
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
1 file changed
tree: 078e6bfc466e7ddb10e568dfabc41df65e38825d
  1. .gitattributes
  2. .gitignore
  3. DEPS
  4. LICENSE
  5. Makefile
  6. PRESUBMIT.py
  7. README.md
  8. STYLEGUIDE.md
  9. android_ingest/
  10. android_stats/
  11. appengine_scripts/
  12. autoroll/
  13. bash/
  14. blamer/
  15. chromeextensions/
  16. codereview.settings
  17. comments/
  18. contest/
  19. cq_watcher/
  20. ct/
  21. datahopper/
  22. datahopper_internal/
  23. debugger/
  24. doc/
  25. fiddle/
  26. flakiness/
  27. fuzzer/
  28. get_service_account/
  29. go/
  30. golden/
  31. grafana/
  32. imageinfo/
  33. infra/
  34. launch.md
  35. logmetrics/
  36. misc/
  37. monitoring/
  38. pdfium/
  39. perdiff/
  40. perf/
  41. power/
  42. prober/
  43. prometheus/
  44. proxy/
  45. pulld/
  46. push/
  47. res/
  48. run_unittests
  49. run_unittests.go
  50. scripts/
  51. skfe/
  52. skolo/
  53. status/
  54. statusv2/
  55. swarming_logger/
  56. task_scheduler/
  57. tools/
  58. tracedb/
  59. webtools/
  60. whitespace.txt
  61. whitespace2.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 github.com/kisielk/errcheck \
  golang.org/x/tools/cmd/goimports \
  github.com/luci/luci-go/client/cmd/isolate
$ npm install -g polylint bower

Build from GOPATH:

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

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.

Use this command to run the presubmit tests:

$ ./run_unittests --small