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 Use to file a bug.
recipe_engine: [third_party] vendor argparse. ( [] Move fetch, lint and bundle parsers to separate modules. ( [] move depgraph arg parsing to its module ( Use "vpython" to bootstrap the recipe engine. ( [] move autoroll arg parsing to its module ( [] move remote arg parsing to its module ( [] move refs arg parsing to its module ( [] move doc arg parsing to its module ( [] move test arg parsing to its module ( [] move run arg parsing to its module. ( [] add missing helpstrings, merge test subcommands into main parser. ( [] move common arg parsing to separate module. ( [autoroll] add tests for autoroll subcommand parsing. ( [fetch] add tests for fetch subcommand parsing. ( [test] add tests for test subcommand parsing. ( [] use argparse to set command automatically. ( [lint] Fix lint to not raise an exception at the end. (,

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I7aa33fb1e3690d7fb9a180a313dab7b0ea28a657
Reviewed-by: Recipe Roller <>
Commit-Queue: Eric Boren <>
1 file changed
tree: 96de7502770fe2ead0a9486791390ddf08b38648
  1. .gitattributes
  2. .gitignore
  3. DEPS
  5. Makefile
  9. android_ingest/
  10. android_stats/
  11. appengine_scripts/
  12. autoroll/
  13. bash/
  14. blamer/
  15. chromeextensions/
  16. codereview.settings
  18. compute_engine_scripts/
  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/
  35. logmetrics/
  36. misc/
  37. pdfium/
  38. perdiff/
  39. perf/
  40. prober/
  41. prometheus/
  42. proxy/
  43. pulld/
  44. push/
  45. res/
  46. run_unittests
  47. run_unittests.go
  48. scripts/
  49. skfe/
  50. skolo/
  51. status/
  52. swarming_logger/
  53. task_scheduler/
  54. tools/
  55. tracedb/
  56. webtools/
  57. whitespace.txt
  58. whitespace2.txt

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 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

This fetches the repository into your $GOPATH directory along with all the Go dependencies. Note: 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 \ \
$ npm install -g polylint bower

Build from GOPATH:

$ cd $GOPATH/src/
$ 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/
$ ./setup_test_db

Running unit tests

Install Cloud SDK.

Use this command to run the presubmit tests:

$ ./run_unittests --small