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/f424d357ecc424dde7c5abfd4f07c28c99397b8b Roll led to git_revision:2f4b9eda0d1860c73abb8e9ab4ad31258f15249a (hinoka@google.com)
  https://crrev.com/6342128c3c8105e02513de27de87d09df7b0a488 [cipd] Add support for ppc64 and ppc64le. (dnj@chromium.org)
  https://crrev.com/1e0b7a5ad455aed94d1961bc481bd1b7ba054e0e [cipd] Fix ppc64le uname. (dnj@chromium.org)
  https://crrev.com/a727b911b6311342d3e77f124d8ee83f8483e90a [vpython,led] Update to new version. (dnj@chromium.org)
  https://crrev.com/d3b2548e57c01853cde9ca3858a3ccb1d9a8bd71 Fix CheckPatchFormatted() error message when using inherit-review-settings-ok (agrieve@chromium.org)
  https://crrev.com/f6a588095f8a73f167fea9b171c7fbdac644da32 Update the CQ patch message. (dpranke@chromium.org)
  https://crrev.com/590420d5d4f580ac69891f36acf8247c2e83b13e Make authors-check error out instead of warn on commit (machenbach@chromium.org)
  https://crrev.com/e6e0641b1536d0b85d11d41977679ab5e562e564 gclient: print an error message instead of crashing (maruel@chromium.org)
  https://crrev.com/037f9b80bbd8b97f54accfcb795cf1241a05c996 bot_update recipe: Upload source manifest (hinoka@google.com)


TBR=borenet@google.com

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

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