mirror of https://github.com/golang/go.git
f579fb3656
Currently we still see some flakes on perf dashboard (e.g. sys-stack is quite frequent). I am planning to run real perf builder with 5 different values of GOMAXPROCS, so we can require 3 builders to agree on a change instead of 2. This will provide 20x improvement in flake detection. At the same time lower noise bar from 1.2 to 1.1, as I see some real perf changes gets ignored as noise. All these magic numbers affect only representation of data, but not the data stored in DB. So we can continue freely tuning them later. There are no significant risks here. LGTM=adg R=adg CC=golang-codereviews https://golang.org/cl/127520044 |
||
|---|---|---|
| .. | ||
| app | ||
| builder | ||
| updater | ||
| README | ||
README
// Copyright 2009 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
The files in this directory constitute the continuous builder:
app/: an AppEngine server
builder/: gobuilder, a Go continuous build client
If you wish to run a Go builder, please email golang-dev@googlegroups.com
To run a builder:
* Write the key ~gobuild/.gobuildkey
You need to get it from someone who knows the key.
You may also use a filename of the form .gobuildkey-$BUILDER if you
wish to run builders for multiple targets.
* Append your username and password googlecode.com credentials from
https://code.google.com/hosting/settings
to the buildkey file in the format "Username\nPassword\n".
(This is for uploading tarballs to the project downloads section,
and is an optional step.)
* Build and run gobuilder (see its documentation for command-line options).