| commit | 3296d56822338680c925c3ee44240fc642ba5ccc | [log] [tgz] |
|---|---|---|
| author | Ravi Mistry <rmistry@google.com> | Fri Aug 16 10:52:11 2019 -0400 |
| committer | Skia Commit-Bot <skia-commit-bot@chromium.org> | Fri Aug 16 15:23:13 2019 +0000 |
| tree | 772c2f3429c0a1e58332061171b4198a7c513890 | |
| parent | 2489d713dc5782ae9373980ac11736374a69ef6f [diff] |
[CT] Operate V8 checkout in detached HEAD and no longer retry gclient sync. The V8 checkout was always giving problems which is why it was the only one that used to do "git reset --hard origin/master". I found https://bugs.chromium.org/p/chromium/issues/detail?id=584742#c8 which explains some of the V8 problems. Trying it out in detached HEAD mode. Also, stop deleting checkouts and retrying gclient sync. It is very time consuming and ends up masking some problems that could be solved in a better way. Eg: V8. Bug: skia:5761 Change-Id: I15395fce1041d1b01fd23f350ce0d3a083685487 Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/235202 Reviewed-by: Ravi Mistry <rmistry@google.com> Commit-Queue: Ravi Mistry <rmistry@google.com>
This repo contains infrastructure code for Skia.
The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone or via go get.
Using git clone allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:
$ cd ${WORKDIR}
$ git clone https://skia.googlesource.com/buildbot.git
$ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR})
$ mkdir $GOPATH
$ cd buildbot
Using go get will fetch the repository into your GOPATH directory along with all the Go dependencies. You will need to set GOPATH and GO111MODULE=on. E.g.:
$ export GOPATH=${WORKDIR}
$ export GO111MODULE=on
$ go get -u -t go.skia.org/infra/...
$ cd ${GOPATH}/src/go.skia.org/infra/
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 ~everything:
$ make all
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 \ github.com/vektra/mockery/...
To generate code run in this directory:
$ go generate ./...
Install Cloud SDK.
Use this command to run the presubmit tests:
$ ./run_unittests --small