Racebuild builds race runtime (syso files) on all supported OSes using gomote.
For now only freebsd is supported.
Usage:
$ racebuild -rev <llvm_revision> -goroot <path_to_go_repo>
The rest should happen automatically (provided you have gomote access).
Update golang/go#8653
Change-Id: Ie9df99860616084471dc92b8dbf369020fbb8f72
Reviewed-on: https://go-review.googlesource.com/16823
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Currently fetchlogs downloads logs to a directory structure created in
the current directory. This makes it difficult to run (you have to
make sure you're in the right directory) and makes it hard for other
tools (e.g., log processing tools) to find these logs.
This change adds a -dir flag to fetchlogs to specify a download
directory. The default value of this flag is derived from the cache
directory of the XDG Base Directory Specification.
Change-Id: I05f01a3db7423250cfef18c42ff38b599b097b35
Reviewed-on: https://go-review.googlesource.com/16818
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This tool downloads build failure logs from the Go dashboard so they
can be accessed and searched from the local file system.
Change-Id: I9d3f90dd8886cb5446d2fb7276c5d24da5c9a8e3
Reviewed-on: https://go-review.googlesource.com/10671
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This allows either overriding the default, or using cmd/upload for
non-builder buckets.
Change-Id: If9a242c9e5cbb4be50768870eec5705b5a265cd5
Reviewed-on: https://go-review.googlesource.com/16800
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This expands the JSON dashboard output to include everything that's
visible on the HTML dashboard (which includes all of the obviously
meaningful fields from the Commit objects).
Change-Id: Ib0437bec276a78ca9efd57fcc16041e40ccd3d4c
Reviewed-on: https://go-review.googlesource.com/16632
Reviewed-by: Andrew Gerrand <adg@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
* status page shows kube pool details
* pods created by the coorindator are tracked
* pods that fail to create are deleted
* pods older than delete-at are deleted
* pods created by a different coordinator are deleted
Updates golang/go#12546
Change-Id: I4c4f8ff906962b4a014a66d0a9d490ff17710d62
Reviewed-on: https://go-review.googlesource.com/16101
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Workaround until the Mac failures are understood.
Updates golang/go#12979
Change-Id: I15b9ea8f4b708ebf9b7c6ad61e65d0f9eaaa6d73
Reviewed-on: https://go-review.googlesource.com/16440
Reviewed-by: David Crawshaw <crawshaw@golang.org>
GCE broke it. GCE is being fixed, but not immediately.
Updates golang/go#13077
Change-Id: I289e382b0a4affc4fc8faee5da053474d1cabc35
Reviewed-on: https://go-review.googlesource.com/16314
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
When trying to resolve a branch name, if there is a remote or tag
of the same name, git cannot resolve it and issues an warning that
"refname 'BRANCH' is ambiguous." This was discovered in gccgo's
watcher process on the branch 'asan' which is also the name of a tag
in the gcc repo. To disambiguate between a remote and a tag, any
refname can be prepended with "heads/" or "tags/", respectively.
Change-Id: I16679f5249a5f22df59ab3a0ed49459bbbf5367b
Reviewed-on: https://go-review.googlesource.com/16083
Reviewed-by: Andrew Gerrand <adg@golang.org>
This adds an auth mode that fetches Gerrit authentication cookies the
same way git does: from the .gitcookies file or from .netrc. This code
is loosely based on the authentication code from git-codereview.
Change-Id: If3c4efc76300b0d2c4b69f7d8af45ebc2a222313
Reviewed-on: https://go-review.googlesource.com/16157
Reviewed-by: Andrew Gerrand <adg@golang.org>
* Replaced cancel with context.Context
* StartPod can be canceled
* Wait for buildlet to come online, but fail fast if pod fails first
* Support timeout waiting for pod to leave pending phase
* Use Kubernetes watch API (long poll)
Updates golang/go#12546
Change-Id: I792a3b8fed615362a0290feee7de0c2cefe43c0e
Reviewed-on: https://go-review.googlesource.com/15285
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Cleans up Makefiles. Correct and much faster now.
Change-Id: I78a7437492d5d1a21b8f7cddf4abffdb70c9c604
Reviewed-on: https://go-review.googlesource.com/15540
Reviewed-by: Andrew Gerrand <adg@golang.org>
Not sure what I was thinking. Hopefully a copy/paste-o.
Fixesgolang/go#12813
Change-Id: Idf63301f8f4098db07c3203575a085f7dab8e6a6
Reviewed-on: https://go-review.googlesource.com/15253
Reviewed-by: Austin Clements <austin@google.com>
* set correct metadata as env vars on each container in pod
* stage0 detects when running in a pod
* add scope to support farmer on GCE communicating with Google
Container Engine API
* dev mode supports GCE and Kubernetes even when not running
on GCE
* pod buildlet returns a configured http.Client
* pod buildlets work, but pods are not removed after completion
(or on creation failure)
Updates golang/go#12546
Change-Id: If91673b49223130c1e7077c130f1abe1e7966d02
Reviewed-on: https://go-review.googlesource.com/15041
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
It's a trybot, but was only using a single machine, making it the long
tail and slowing down trybot results.
Change-Id: I09ccc56b3866d522e4abf96215a2e293aed4e4d6
Reviewed-on: https://go-review.googlesource.com/14954
Reviewed-by: David Crawshaw <crawshaw@golang.org>
Find the default Kubernetes cluster and configure a client to talk to it.
Use application default credentials.
Updates golang/go#12546
Change-Id: Ifb1ce57f52f4fbbee3267f8cc3cf02a78146bd5b
Reviewed-on: https://go-review.googlesource.com/14532
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This CL makes the main buildlet and any helper buildlets all
equivalent once we get to the final stage of the build (test
execution). Now the death of the main buildlet isn't critical and the
testing continues as long as any buildlet is alive (or any helper
buildlet is on its way).
It also makes timeouts (20 minutes) of remote commands fatal, now that
health checking is reliable for all buildlet types.
Fixesgolang/go#12685
Change-Id: I07d1e1fabf1027ee24ce679e4fcc8bd09bed6d83
Reviewed-on: https://go-review.googlesource.com/14774
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
We were creating corrupt snapshots before (golang/go#12671), so
double-check them before use, for now. We can relax this in the future
(see TODO).
Fixesgolang/go#12671
Change-Id: I10b7929d4b78c717f29c67a0ce495ecd435a1d26
Reviewed-on: https://go-review.googlesource.com/14772
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Alpha introduced a problem with "docker logs":
https://groups.google.com/forum/#!topic/coreos-user/VhqeIjkO2VA
So, revert for now. No need for bleeding edge.
Also, be sure to make the coordinator's service declaration restarts on
failure, even if there are many errors in a row. (I learned this the
hard way with another project and just realized this service file
omits the StartLimitInterval=0 line to disable the rate limit)
Change-Id: I9717e3b665bd4540d3cf4921018b619af1539178
Reviewed-on: https://go-review.googlesource.com/14771
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
The previous blacklisting was because of golang/go#12668, since fixed.
Further, the tests are now sharded (golang/go#12623) and this test
name doesn't even exist, so this change is a no-op.
Change-Id: Id141923e904a5aec91e53ba6f1d44e6cdf137cd2
Reviewed-on: https://go-review.googlesource.com/14773
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Previously it wasn't noticing their death until the next health check.
Take advantage of that the revdial is always blocked in a Read, so it
will see a TCP shutdown in the case of normal shutdowns. (health checks
will still catch disappearing machines)
Change-Id: I9a7f60a38b3acaf02057b2da9e0cbc91d328f651
Reviewed-on: https://go-review.googlesource.com/14736
Reviewed-by: Andrew Gerrand <adg@golang.org>
Also show build steps with -x in Makefile. It's slow to use go build,
but go install doesn't quite work. Need to figure that out.
Change-Id: I79093dc7c84912b3f04c9e4708c9f65086c4445c
Reviewed-on: https://go-review.googlesource.com/14733
Reviewed-by: Andrew Gerrand <adg@golang.org>
I noticed some hung forever during the initial connect + TLS handshake, which
can happen if the server is restarted/rebooted and TCP connections hang.
Change-Id: I4ada86aa2e5629b82de27fa6cfea376211490068
Reviewed-on: https://go-review.googlesource.com/14734
Reviewed-by: Andrew Gerrand <adg@golang.org>
It was not producing correct results before.
Change-Id: I77c857e8064ad36a5fdb982507b265271beb7bbd
Reviewed-on: https://go-review.googlesource.com/14735
Reviewed-by: Andrew Gerrand <adg@golang.org>
Works for detecting new flaky builds from different pages, but I
can't actually clear them yet. (caching bug in the dashboard?)
Change-Id: Iad9c3a5aef2016a81ad71559bb140044b68e42e2
Reviewed-on: https://go-review.googlesource.com/14732
Reviewed-by: Andrew Gerrand <adg@golang.org>
should be rare now.
Change-Id: Icc4bfd13c8dfe8f2e189db819bc0d552f35fb3c9
Reviewed-on: https://go-review.googlesource.com/14731
Reviewed-by: Andrew Gerrand <adg@golang.org>
Use the new Go 1.5 mechanism to abort HTTP requests with a channel.
This is respected by the Go 1.5 http.Transport, which we always use.
This CL shouldn't be necessary (CL 14700 was the real bug), but
doesn't hurt. This still would've probably prevented most of
golang/go#12666
Change-Id: I6890e016ee04183fc0d600baed8046c2f79113d8
Reviewed-on: https://go-review.googlesource.com/14701
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
If the server's conn stopped reading, we acquired a Lock twice
(blocking forever) and never killing all the active connections on it.
Add test.
Probably fixesgolang/go#12666
Change-Id: I4ff670a55e8d92e6e2ebe14a94137d6f15f3768e
Reviewed-on: https://go-review.googlesource.com/14700
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Dmitry Vyukov
Brad Fitzpatrick
Austin Clements
Evan Brown
Andrew Gerrand
David Crawshaw
Matthew Dempsky
Chris Manghane
Brad Fitzpatrick
Matt Drollette