Introduction

Builders that are managed by the coordinator (VMs running on GCE or reverse buildlets, such as the new OS X builders) are listed here:

http://farmer.golang.org/builders

For design details about the coordinator, see http://golang.org/s/builderplan

Older-style builders are listed below. These builders are configured and run manually. The goal is to migrate as many as possible over to the new system.

titledescriptionownernotes
linux-arm64-canonicalARMv8@davecheneyUbuntu 14.04
linux-arm64-linaroARMv8@davecheneyUbuntu 14.04.2
linux-ppc64le-canonicalPOWER8 little endian@davecheneyUbuntu 14.04
android-arm-crawshawNexus 7crawshawBuilder runs on attached desktop, uses adb
darwin-amd642011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
darwin-amd64-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
darwin-amd64-race-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
darwin-3862011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
darwin-386-cheney2011 Mac Mini, 2.4Ghz Core i5Dave CheneyMac OS X 10.10 XCode 5
dragonfly-amd64?Justin Sherrill?
linux-arm-luitvdRaspberryPiLuit van Drongelen
linux-arm-arm5QNAP TS-119P, ARMv5 @ 2.0GHz, 512MBDave CheneyGOARM=5
linux-arm-cheney-imx6Solidrun Cubox-i, quad core Cortex-A9 ~ 1Ghz, 2Gb ramDave CheneyRuns arch linux, iMX6 boards need 3.10.x or above to pass the build reliably
linux-ppc64KVM instance on physical 8-core POWER7 pSeries. Chip rev: 2.1 (pvr 004b 0201)bradfitz, rsc
linux-ppc64-minuxGentoo on PowerMac G5 (dual 2.7GHz ppc970fx)minux
linux-mips64le-cherryGentoo on Loongson 2F 800MHz, 1GB DDR2cherrybuilds sharded on three machines
linux-mips64le-stitchCavium Octeon II CN6880, 32-core @ 1GHz, 8GB RAMEd SwierkDebian sid, no FPU
linux-mips64-minuxGentoo on EdgeRouter Lite, 500MHz dual core MIPS64r2, 512MBminux
nacl-armsamsung chromebookrscrunning chrubuntu
nacl-arm-cheneysame builder as linux-arm-cheney-imx6Dave Cheney
netbsd-386-minuxKVMminux
netbsd-amd64-bsiegertEC2 m1.small VMBenny Siegerton Brad's work EC2 account
openbsd-armSolidRun CuBox-i4Pro, ARM Cortex A9 R2 792 MHz, 2GB RAMJoel Sing
plan9-386-ducolombierIntel Core 2 Quad Q8200 2.33 GHz, 6GBDavid du ColombierPlan 9 from Bell Labs
plan9-armRaspberry Pi 3 Model BDavid du ColombierPlan 9 from Bell Labs
plan9-amd64-9frontVMDavid du Colombier9front
solaris-amd64-smartosE5-1650 Xeon, 6C/12TDaniel Malonruns illumos (smartos zone); dfc, aram have full access
solaris-amd64-solaris11VMDave Cheneyruns Solaris 11

Builder Requirements

  • internet connection (at least be able to access Google and http://build.golang.org)
  • preferably with two or more (V)CPUs, as at least one test (sync/atomic requires runtime.NumCPU() > 1 to test more completely)
  • at least 512MiB of memory (1GB or more highly recommended. 512MB might need a small GOGC setting to avoid thrashing.)

Restrictions

  • The combination of Ubuntu 11.10 or 12.04 OMAP4 kernel and pandaboard (ES) have proven unstable as builders. See issue 4305. Make sure you have updated to the latest available 12.04.2 release.

How to set up a builder

  1. obtain a hash from Go team members, and put that in ~/.gobuildkey
  2. go get golang.org/x/build/cmd/builder
  3. builder YOUR_BUILDER_NAME

Special notes

  • Please make sure you‘ve installed root certificates and that it’s accessible to Go programs. For example, on NetBSD, you will need to install security/mozilla-rootcerts.
  • If your builder runs Unix, please install perl, as tests for go.tools/cmd/vet need it.
  • Use screen(1) instead of tmux(1) to host the builder process, as the later interferes with some of the os/signal tests.
  • Raise ulimits on Unix: thread count (-r), nofiles (-n, 1024 should be fine)