Coordinator-managed builders

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

Old-style builders

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
android-arm-crawshawNexus 7crawshawBuilder runs on attached desktop, uses adb
darwin-amd642011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
darwin-3862011 Mac Mini, 2.4Ghz Core i5adgMac OS X 10.6 (10K549)
dragonfly-amd64?Justin Sherrill?
freebsd-arm-paulzholCubiboard2 1Gb RAM dual-core Cortex-A7 (Allwiner A20)Yuval Pavel ZholkoverFreeBSD 11 r299674 with NODEBUG kernel (w/o INVARIANTS, WITNESS, DEADLKRES)
linux-arm-luitvdRaspberryPiLuit van Drongelen
linux-ppc64Power8E big endianbradfitz, rsc
linux-ppc64-minuxGentoo on PowerMac G5 (dual 2.7GHz ppc970fx)minuxDisabled, Go doesn't support ppc970 anymore
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-cheneyRaspberry Pi 3@davecheney
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.
  • Raise ulimits on Unix: thread count (-r), nofiles (-n, 1024 should be fine)