Google Git
Sign in
skia / buildbot / 458de57d4d2ac63a757e0c8f9a7bc66485374c86
commit458de57d4d2ac63a757e0c8f9a7bc66485374c86[log] [tgz]
authorKevin Lubick <kjlubick@google.com>Tue Apr 25 10:54:58 2017 -0400
committerSkia Commit-Bot <skia-commit-bot@chromium.org>Tue Apr 25 15:03:21 2017 +0000
tree156f51e8ae5944bdef76ec70382d72b9ef6bfdef
parent3c7a38437198d60002045c5709356770624afa69 [diff]
[fuzzer] Fix rolling logic

I missed a plumbing step on the front end side.
Made backend more resistent to 404 errors.
It appears that by using httputils.NewBackOffTransport(), storage.ErrObjNotExist
is not thrown because the API doesn't know how to deal with its errors.
To compensate, we check for 404 in the error message because BackoffTransport
includes it in the message.

Also tweak the release to work, since the css was removed.

Bug: skia:6094
Change-Id: I753cd4422fb30d44a5f8ebfbfbd592a6ab8ffe9c
Reviewed-on: https://skia-review.googlesource.com/13965
Reviewed-by: Kevin Lubick <kjlubick@google.com>
Commit-Queue: Kevin Lubick <kjlubick@google.com>
4 files changed
tree: 156f51e8ae5944bdef76ec70382d72b9ef6bfdef
  1. android_ingest/
  2. android_stats/
  3. appengine_scripts/
  4. autoroll/
  5. bash/
  6. blamer/
  7. chromeextensions/
  8. comments/
  9. compute_engine_scripts/
  10. cq_watcher/
  11. ct/
  12. datahopper/
  13. datahopper_internal/
  14. debugger/
  15. doc/
  16. fiddle/
  17. flakiness/
  18. fuzzer/
  19. get_service_account/
  20. go/
  21. golden/
  22. grafana/
  23. grandcentral/
  24. imageinfo/
  25. infra/
  26. logmetrics/
  27. misc/
  28. nsqd/
  29. pdfium/
  30. perdiff/
  31. perf/
  32. prober/
  33. prometheus/
  34. proxy/
  35. pulld/
  36. push/
  37. res/
  38. scripts/
  39. skfe/
  40. skolo/
  41. status/
  42. task_scheduler/
  43. tools/
  44. tracedb/
  45. webtools/
  46. .gitattributes
  47. .gitignore
  48. codereview.settings
  49. DEPS
  50. launch.md
  51. LICENSE
  52. Makefile
  53. PRESUBMIT.py
  54. README.md
  55. run_unittests
  56. run_unittests.go
  57. STYLEGUIDE.md
  58. whitespace.txt
  59. 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