Open kevinburke opened 7 years ago
These may be good issues for beginners; here's the .travis.yml
file I'm using.
sudo: required
language: go
go_import_path: golang.org/x/build
services:
- docker
before_install:
# Hack to work around https://github.com/golang/go/issues/20423.
- go get go4.org/syncutil
go:
- 1.8
- 1.9
- tip
script:
- go vet ./... || true
- go test -v -race ./...
- pushd cmd/coordinator && make docker-staging && popd
- pushd cmd/gitmirror && make docker-staging && popd
- pushd cmd/gopherbot && make docker-staging && popd
- pushd cmd/pubsubhelper && make docker-staging && popd
- pushd devapp && make docker-staging && popd
- pushd maintner/maintnerd && make docker-staging && popd
What do you think is best for TestCorpusCheck
? Maybe generate some fake test data on the fly? I think that'd involve fixing other tests where they're explicitly looking for a particular commit ID, parent and so on.
In lieu of an automated builder, I run the x/build tests in Travis CI. @andybons has fixed two problems with cmd/cl and with cloud.google.com depedencies, but this has revealed a number of underlying test failures:
TestCorpusCheck
causes the entire Go corpus to download to the test instance, which eventually runs out of memory.Also, we need to update the
go-github
version for thegitmirror
Docker file, I believe; IsPullRequest was added very recently.