go
/
build
зеркало из https://github.com/golang/build.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
build/dashboard/builders.go

3243 строки
108 KiB
Go
Исходник Обычный вид История

dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
// Copyright 2015 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.
// Package dashboard contains shared configuration and logic used by various
// pieces of the Go continuous build system.
package dashboard
buildlet, cmd/coordinator: GCE quota accounting, fixes And deal with Preemptible resource exhaustion errors. And change all-compile to misc-compile and only do the builders not covered otherwise (Fixes #11073) And make the watcher serve git source. And cache and singleflight fetching of git source. And a million other things. Fixes golang/go#11073 Change-Id: I0f45610f0c6a06bd0c8ba9632b8624e00aeb52fc Reviewed-on: https://go-review.googlesource.com/10750 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-05 04:25:50 +03:00
import (
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
"fmt"
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
"os"
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
"sort"
buildlet, cmd/coordinator: GCE quota accounting, fixes And deal with Preemptible resource exhaustion errors. And change all-compile to misc-compile and only do the builders not covered otherwise (Fixes #11073) And make the watcher serve git source. And cache and singleflight fetching of git source. And a million other things. Fixes golang/go#11073 Change-Id: I0f45610f0c6a06bd0c8ba9632b8624e00aeb52fc Reviewed-on: https://go-review.googlesource.com/10750 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-05 04:25:50 +03:00
"strconv"
"strings"
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
"time"
all: consolidate configuration for coordinator and gomote buildenv.Environment type defines configuration options: - Coordinator uses the GCE project name to lookup config. A custom config name can be provided at runtime to override. - The conventional prod and stage project names ('symbolic-datum-552' and 'go-dashboard-dev') map to prod and staging configuration structs. - Production and staging status is explicitly defined in configuration. - GCS bucket names for buildlet, logs, and snapshots are configurable. Change-Id: I7e6d7874eb0bdfe35dbdd5fcf6212ab50d576b88 Reviewed-on: https://go-review.googlesource.com/19502 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-02-15 02:59:59 +03:00
"golang.org/x/build/buildenv"
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
"golang.org/x/build/internal/gophers"
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
"golang.org/x/build/maintner/maintnerd/maintapi/version"
dashboard, cmd/coordinator, maintner/maintnerd: add support for BuildConfig.MinimumGoVersion field The new BuildConfig.MinimumGoVersion field specifies the minimum Go version the builder is allowed to use. It's useful when some of the builders are too new, and do not support all of the supported Go releases (e.g., openbsd-amd64-64 and freebsd-amd64-12_0 currently require Go 1.11 and don't work on Go 1.10). It only needs to be set when a builder doesn't support all supported Go releases, since we don't typically test unsupported Go releases. To allow cmd/coordinator to use this field and filter out work it receives from maintner/maintnerd's GoFindTryWork RPC call, we add a GoVersion slice to apipb.GerritTryWorkItem, and populate it in maintapi.apiService.GoFindTryWork method. For trybots on the Go repo, the GoVersion field is determined from the branch name. For "release-branch.goX.Y" branches, it parses out the major-minor Go version from the branch name. For master and other branches, it assumes the latest Go release. For trybots on subrepos, we already have the Go version information available, so use it directly. Afterwards, all that's left is to modify newTrySet in cmd/coordinator to make use of BuildConfig.MinimumGoVersion and work.GoVersion to skip builders that are too new for the Go version that needs to be tested. Fixes golang/go#29265 Change-Id: I50b01830647e33e37e9eb8b89e0f2518812fa44f Reviewed-on: https://go-review.googlesource.com/c/155463 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-01-12 00:44:01 +03:00
"golang.org/x/build/types"
buildlet, cmd/coordinator: GCE quota accounting, fixes And deal with Preemptible resource exhaustion errors. And change all-compile to misc-compile and only do the builders not covered otherwise (Fixes #11073) And make the watcher serve git source. And cache and singleflight fetching of git source. And a million other things. Fixes golang/go#11073 Change-Id: I0f45610f0c6a06bd0c8ba9632b8624e00aeb52fc Reviewed-on: https://go-review.googlesource.com/10750 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-05 04:25:50 +03:00
)
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
cmd/coordinator: add SlowBots support, opt-in to different slow trybots This parses TRY= comments to opt-in to slower/difference trybots. This needs some docs/UI work yet. Updates golang/go#34501 Change-Id: I13a835520d7ac341bc86139b0a2118235bc83e60 Reviewed-on: https://go-review.googlesource.com/c/build/+/201338 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-16 09:02:29 +03:00
// slowBotAliases maps short names from TRY= comments to which builder to run.
//
// TODO: we'll likely expand this, or move it, or change the matching
// syntax entirely. This is a first draft.
var slowBotAliases = map[string]string{
// Known missing builders:
dashboard,cmd/release: replace windows-arm64-aws with windows-arm64-10 This change removes the windows-arm64-aws buildlet and replaces all usages with the windows-arm64-10 buildlet. - Remove the known issue from the windows-arm64-10 buildlet, which has been passing reliably. - Enable tests during releases, and add a slowbot alias, as it's a much faster buildlet. Updates golang/go#46502 For golang/go#42604 Change-Id: Ib9f7c3d5391b01e303b43bbdad030b3f94147c5d Reviewed-on: https://go-review.googlesource.com/c/build/+/331670 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-29 18:40:03 +03:00
"ios-amd64": "", // There is no builder for the iOS Simulator. See issues 42100 and 42177.
cmd/coordinator: add SlowBots support, opt-in to different slow trybots This parses TRY= comments to opt-in to slower/difference trybots. This needs some docs/UI work yet. Updates golang/go#34501 Change-Id: I13a835520d7ac341bc86139b0a2118235bc83e60 Reviewed-on: https://go-review.googlesource.com/c/build/+/201338 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-16 09:02:29 +03:00
all: add linux-ppc64le-power10-osu builder This builder requires a patched bootstrap toolchain to accept GOPPC64=power10. Likewise, this folds in a change to update the container images to ubuntu 20.04. This is and has been running on the existing ppc64le builders for a couple months already. Change-Id: Ia86cb711c99c0d8ab5f9de0ae50129fe11e6ccab Reviewed-on: https://go-review.googlesource.com/c/build/+/454515 Run-TryBot: Paul Murphy <murp@ibm.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org>
2022-12-01 01:50:25 +03:00
"386": "linux-386",
"aix": "aix-ppc64",
"amd64": "linux-amd64",
"android": "android-amd64-emu",
"android-386": "android-386-emu",
"android-amd64": "android-amd64-emu",
"android-arm": "android-arm-corellium",
"android-arm64": "android-arm64-corellium",
"arm": "linux-arm-aws",
"arm64": "linux-arm64",
"darwin": "darwin-amd64-12_0",
"darwin-amd64": "darwin-amd64-12_0",
"darwin-arm64": "darwin-arm64-12",
"ios-arm64": "ios-arm64-corellium",
"dragonfly": "dragonfly-amd64-622",
"dragonfly-amd64": "dragonfly-amd64-622",
"freebsd": "freebsd-amd64-13_0",
"freebsd-386": "freebsd-386-13_0",
"freebsd-amd64": "freebsd-amd64-13_0",
"freebsd-arm": "freebsd-arm-paulzhol",
"freebsd-arm64": "freebsd-arm64-dmgk",
"freebsd-riscv64": "freebsd-riscv64-unmatched",
"illumos": "illumos-amd64",
"ios": "ios-arm64-corellium",
"js": "js-wasm",
"linux": "linux-amd64",
"linux-arm": "linux-arm-aws",
"linux-loong64": "linux-loong64-3a5000",
"linux-mips": "linux-mips-rtrk",
"linux-mips64": "linux-mips64-rtrk",
"linux-mips64le": "linux-mips64le-rtrk",
"linux-mipsle": "linux-mipsle-rtrk",
"linux-ppc64": "linux-ppc64-sid-buildlet",
"linux-ppc64le": "linux-ppc64le-buildlet",
"linux-ppc64le-power9": "linux-ppc64le-power9osu",
"linux-ppc64le-power10": "linux-ppc64le-power10osu",
"linux-riscv64": "linux-riscv64-unmatched",
"linux-s390x": "linux-s390x-ibm",
"longtest": "linux-amd64-longtest",
"loong64": "linux-loong64-3a5000",
"mips": "linux-mips-rtrk",
"mips64": "linux-mips64-rtrk",
"mips64le": "linux-mips64le-rtrk",
"mipsle": "linux-mipsle-rtrk",
"netbsd": "netbsd-amd64-9_3",
"netbsd-386": "netbsd-386-9_3",
"netbsd-amd64": "netbsd-amd64-9_3",
"netbsd-arm": "netbsd-arm-bsiegert",
"netbsd-arm64": "netbsd-arm64-bsiegert",
"nocgo": "linux-amd64-nocgo",
"openbsd": "openbsd-amd64-70",
"openbsd-386": "openbsd-386-70",
"openbsd-amd64": "openbsd-amd64-70",
"openbsd-arm": "openbsd-arm-jsing",
"openbsd-arm64": "openbsd-arm64-jsing",
"openbsd-mips64": "openbsd-mips64-jsing",
"plan9": "plan9-arm",
"plan9-386": "plan9-386-0intro",
"plan9-amd64": "plan9-amd64-0intro",
"ppc64": "linux-ppc64-sid-buildlet",
"ppc64le": "linux-ppc64le-buildlet",
"ppc64lep9": "linux-ppc64le-power9osu",
"ppc64lep10": "linux-ppc64le-power10osu",
"riscv64": "linux-riscv64-unmatched",
"s390x": "linux-s390x-ibm",
"solaris": "solaris-amd64-oraclerel",
"solaris-amd64": "solaris-amd64-oraclerel",
"wasm": "js-wasm",
"windows": "windows-amd64-2016",
"windows-386": "windows-386-2008",
"windows-amd64": "windows-amd64-2016",
"windows-arm": "windows-arm-zx2c4",
"windows-arm64": "windows-arm64-11",
cmd/coordinator: add SlowBots support, opt-in to different slow trybots This parses TRY= comments to opt-in to slower/difference trybots. This needs some docs/UI work yet. Updates golang/go#34501 Change-Id: I13a835520d7ac341bc86139b0a2118235bc83e60 Reviewed-on: https://go-review.googlesource.com/c/build/+/201338 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-16 09:02:29 +03:00
}
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
// Builders are the different build configurations.
// The keys are like "darwin-amd64" or "linux-386-387".
// This map should not be modified by other packages.
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
// Initialization happens below, via calls to addBuilder.
all: change dashboard.BuildConfig to be a pointer type, like HostConfig BuildConfig grew way too large and has too many slices & such to be a value type. Make it a pointer type, which matches HostConfig. Change-Id: Ie625bece9d6d8c1ec6cff26e77416bd9b1f256d8 Reviewed-on: https://go-review.googlesource.com/c/145077 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 20:52:25 +03:00
var Builders = map[string]*BuildConfig{}
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
// GoBootstrap is the bootstrap Go version.
// Bootstrap Go builds with this name must be in the bucket,
// usually uploaded by 'genbootstrap -upload all'.
const GoBootstrap = "go1.17.13"
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
// Hosts contains the names and configs of all the types of
// buildlets. They can be VMs, containers, or dedicated machines.
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
//
// Please keep table sorted by map key.
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
var Hosts = map[string]*HostConfig{
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-aix-ppc64-osuosl": {
Notes: "AIX 7.2 VM on OSU; run by Tony Reix",
Owners: []*gophers.Person{gh("trex58")},
IsReverse: true,
ExpectNum: 1,
},
"host-android-arm64-corellium-android": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
Notes: "Virtual Android devices hosted by Zenly on Corellium; see issues 31722 and 40523",
Owners: []*gophers.Person{gh("steeve"), gh("changkun")}, // See https://groups.google.com/g/golang-dev/c/oiuIE7qrWp0.
IsReverse: true,
ExpectNum: 3,
GoBootstrap: "none", // image has Go 1.15.3 (go.dev/issue/54246); cannot access storage.googleapis.com
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
env: []string{
"GOROOT_BOOTSTRAP=/data/data/com.termux/files/home/go-android-arm64-bootstrap",
// Only run one job at a time to avoid the OOM killer.
// Issue 50084.
"GOMAXPROCS=1",
},
},
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
"host-darwin-amd64-10_14-aws": {
IsReverse: true,
ExpectNum: 2,
Notes: "AWS macOS Mojave (10.14) VM under QEMU",
SSHUsername: "gopher",
HermeticReverse: true, // we destroy the VM when done & recreate
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
GoogleReverse: true,
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
},
"host-darwin-amd64-10_15-aws": {
IsReverse: true,
ExpectNum: 2,
Notes: "AWS macOS Catalina (10.15) VM under QEMU",
SSHUsername: "gopher",
HermeticReverse: true, // we destroy the VM when done & recreate
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
GoogleReverse: true,
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
},
"host-darwin-amd64-11-aws": {
IsReverse: true,
ExpectNum: 2,
Notes: "AWS macOS Big Sur (11) VM under QEMU",
SSHUsername: "gopher",
HermeticReverse: true, // we destroy the VM when done & recreate
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
GoogleReverse: true,
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
},
dashboard: add darwin-amd64 AWS reverse builder Used for AWS Mac prototyping. For #48945. Change-Id: Icd0d72ca1ad1b8d4dc6d843c4899d2207d8c6f9e Reviewed-on: https://go-review.googlesource.com/c/build/+/430696 Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-09-13 23:03:19 +03:00
"host-darwin-amd64-12-aws": {
IsReverse: true,
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
ExpectNum: 2,
Notes: "AWS macOS Monterey (12) VM under QEMU",
dashboard: add darwin-amd64 AWS reverse builder Used for AWS Mac prototyping. For #48945. Change-Id: Icd0d72ca1ad1b8d4dc6d843c4899d2207d8c6f9e Reviewed-on: https://go-review.googlesource.com/c/build/+/430696 Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-09-13 23:03:19 +03:00
SSHUsername: "gopher",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
HermeticReverse: true, // we destroy the VM when done & recreate
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
GoogleReverse: true,
dashboard: add darwin-amd64 AWS reverse builder Used for AWS Mac prototyping. For #48945. Change-Id: Icd0d72ca1ad1b8d4dc6d843c4899d2207d8c6f9e Reviewed-on: https://go-review.googlesource.com/c/build/+/430696 Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-09-13 23:03:19 +03:00
},
dashboard: add darwin 13 (Ventura) amd64 builders on AWS For golang/go#48945. For golang/go#55355. Change-Id: Ic8f346995024c69a3a8f2b91681e4ff90280f2c6 Reviewed-on: https://go-review.googlesource.com/c/build/+/448435 Auto-Submit: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-07 21:19:29 +03:00
"host-darwin-amd64-13-aws": {
IsReverse: true,
ExpectNum: 2,
Notes: "AWS macOS Ventura (13) VM under QEMU",
SSHUsername: "gopher",
HermeticReverse: true, // we destroy the VM when done & recreate
GoogleReverse: true,
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-darwin-arm64-11": {
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
IsReverse: true,
Notes: "macOS Big Sur (11) ARM64 (M1) on Mac minis in a Google office",
ExpectNum: 3,
SSHUsername: "gopher",
GoogleReverse: true,
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-darwin-arm64-12": {
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
IsReverse: true,
ExpectNum: 3,
dashboard: fix typo in host-darwin-arm64-12 description The current releaselet descriptions are good, as recently discussed, leaving just one typo in the macOS version name to fix up to reduce confusion. Change-Id: I60d12dcc67c2bfa4842b081b0c0e950faa50a067 Reviewed-on: https://go-review.googlesource.com/c/build/+/452856 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-22 23:52:05 +03:00
Notes: "macOS Monterey (12) ARM64 (M1) on Mac minis in a Google office",
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
SSHUsername: "gopher",
GoogleReverse: true,
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
dashboard: use dragonfly on GCE for dragonfly-amd64 builds Now that we have DragonflyBSD on GCE, use it instead of the single reverse builder provided by the DragonflyBSD team. A full 'debugnewvm' all.bash run, including starting the VM, takes 12 minutes, which is rather a lot faster than the current machine. Fixes golang/go#23060. Fixes golang/go#45215. Fixes golang/go#53577. Change-Id: Icb6e5cfde2e8c7ff16fa03cbc0eb833b275180ef Reviewed-on: https://go-review.googlesource.com/c/build/+/419084 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-22 19:20:28 +03:00
"host-dragonfly-amd64-622": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
Notes: "DragonFly BSD 6.2.2 on GCE, built from build/env/dragonfly-amd64",
VMImage: "dragonfly-amd64-622",
SSHUsername: "root",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-freebsd-amd64-12_3": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "freebsd-amd64-123-stable-20211230",
Notes: "FreeBSD 12.3; GCE VM, built from build/env/freebsd-amd64",
SSHUsername: "gopher",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-freebsd-amd64-13_0": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "freebsd-amd64-130-stable-20211230",
Notes: "FreeBSD 13.0; GCE VM, built from build/env/freebsd-amd64",
SSHUsername: "gopher",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-freebsd-arm-paulzhol": {
IsReverse: true,
ExpectNum: 1,
dashboard: update freebsd-arm-paulzhol Note, remove 52679 from KnownIssues TestPreemptionAfterSyscall and runtime/pprof no longer fail, after the builder was upgraded. Hardware wise, it's an ARM Cortex A7 -> Cortex A53 (in 32bit mode). FreeBSD 13.0 -> 13.1 and also switched from the default SCHED_ULE to SCHED_4BSD. Update golang/go#52679. Change-Id: Id2be185992c07d74e43e254cd54133b605b1d06e Reviewed-on: https://go-review.googlesource.com/c/build/+/420354 Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
2022-07-30 21:29:41 +03:00
Notes: "Raspberry Pi 3 Model B, FreeBSD 13.1-RELEASE with SCHED_4BSD",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
Owners: []*gophers.Person{gh("paulzhol")},
},
"host-freebsd-arm64-dmgk": {
IsReverse: true,
ExpectNum: 1,
Notes: "AWS EC2 a1.large 2 vCPU 4GiB RAM, FreeBSD 12.1-STABLE",
Owners: []*gophers.Person{gh("dmgk")},
},
build/dashboard: add freebsd-riscv64 Fixes golang/go#53466. Change-Id: Icb95b00ce2f82620add81080a3f6d589586a19ab Reviewed-on: https://go-review.googlesource.com/c/build/+/425937 Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-08-26 22:41:14 +03:00
"host-freebsd-riscv64-unmatched": {
dashboard: freebsd-riscv64 bootstrap from local The port of freebsd-riscv64 is still working in progresss means bootstrap binary from GCP is unavailable for now. For golang/go#53466 Change-Id: I81ee945e0f0bc95be980e1f2a3d5f61c42e37f28 Reviewed-on: https://go-review.googlesource.com/c/build/+/434295 Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-09-26 06:45:21 +03:00
IsReverse: true,
ExpectNum: 1,
Notes: "SiFive HiFive Unmatched RISC-V board. 16 GB RAM. FreeBSD 13.1-RELEASE",
Owners: []*gophers.Person{gh("mengzhuo")},
GoBootstrap: "none",
env: []string{
"GOROOT_BOOTSTRAP=/home/gopher/go-freebsd-riscv64-bootstrap",
},
build/dashboard: add freebsd-riscv64 Fixes golang/go#53466. Change-Id: Icb95b00ce2f82620add81080a3f6d589586a19ab Reviewed-on: https://go-review.googlesource.com/c/build/+/425937 Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-08-26 22:41:14 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-illumos-amd64-jclulow": {
Notes: "SmartOS base64@19.1.0 zone",
Owners: []*gophers.Person{gh("jclulow")},
IsReverse: true,
ExpectNum: 1,
SSHUsername: "gobuild",
},
"host-ios-arm64-corellium-ios": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
Notes: "Virtual iOS devices hosted by Zenly on Corellium; see issues 31722 and 40523",
Owners: []*gophers.Person{gh("steeve"), gh("changkun")}, // See https://groups.google.com/g/golang-dev/c/oiuIE7qrWp0.
IsReverse: true,
ExpectNum: 3,
GoBootstrap: "none", // image has devel d6c4583ad4 (pre-Go 1.18) Dec 2021 (go.dev/issue/54246); cannot access storage.googleapis.com
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
env: []string{
"GOROOT_BOOTSTRAP=/var/root/go-ios-arm64-bootstrap",
},
},
"host-linux-amd64-alpine": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Alpine container",
ContainerImage: "linux-x86-alpine:latest",
SSHUsername: "root",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
dashboard: rename host-android-amd64-emu to host-linux-amd64-androidemu This follows the name convention and avoids a HostArch line. For golang/go#44505. Change-Id: I14654e64751ee830101e1191bd44cd426b3ecce2 Reviewed-on: https://go-review.googlesource.com/c/build/+/420804 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-08-03 22:43:12 +03:00
"host-linux-amd64-androidemu": {
all: switch vmx-enabled Debian over to Bullseye I basically just did a find-and-replace, and we'll see if it works? I've updated and built the new disk images so this should be ready to deploy. For golang/go#56414. Change-Id: Iaac41d6f7a1244c3682e624f7a4ee4fa7477dfa1 Reviewed-on: https://go-review.googlesource.com/c/build/+/445617 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:01:19 +03:00
Notes: "Debian Bullseye w/ Android SDK + emulator (use nested virt)",
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
ContainerImage: "android-amd64-emu:bff27c0c9263",
all: switch vmx-enabled Debian over to Bullseye I basically just did a find-and-replace, and we'll see if it works? I've updated and built the new disk images so this should be ready to deploy. For golang/go#56414. Change-Id: Iaac41d6f7a1244c3682e624f7a4ee4fa7477dfa1 Reviewed-on: https://go-review.googlesource.com/c/build/+/445617 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:01:19 +03:00
KonletVMImage: "android-amd64-emu-bullseye",
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
NestedVirt: true,
SSHUsername: "root",
dashboard: rename host-android-amd64-emu to host-linux-amd64-androidemu This follows the name convention and avoids a HostArch line. For golang/go#44505. Change-Id: I14654e64751ee830101e1191bd44cd426b3ecce2 Reviewed-on: https://go-review.googlesource.com/c/build/+/420804 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-08-03 22:43:12 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-bullseye": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian Bullseye",
ContainerImage: "linux-x86-bullseye:latest",
SSHUsername: "root",
env/linux-x86-bullseye, dashboard: add Debian Bullseye builder This change adds the host-linux-bullseye host as well as the configuration for the host. The linux-amd64-bullseye builder has been added in this change as well. Fixes golang/go#47720 Change-Id: I607f937133a0db3ed6a841f53dc7fef5e310a5a4 Reviewed-on: https://go-review.googlesource.com/c/build/+/342630 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-08-16 22:35:39 +03:00
},
all: switch vmx-enabled Debian over to Bullseye I basically just did a find-and-replace, and we'll see if it works? I've updated and built the new disk images so this should be ready to deploy. For golang/go#56414. Change-Id: Iaac41d6f7a1244c3682e624f7a4ee4fa7477dfa1 Reviewed-on: https://go-review.googlesource.com/c/build/+/445617 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:01:19 +03:00
"host-linux-amd64-bullseye-vmx": {
Notes: "Debian Bullseye w/ Nested Virtualization (VMX CPU bit) enabled",
ContainerImage: "linux-x86-bullseye:latest",
NestedVirt: true,
SSHUsername: "root",
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-buster": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian Buster",
ContainerImage: "linux-x86-buster:latest",
SSHUsername: "root",
env/linux-x86-buster: add Debian Buster builder This change adds a Debian Buster builder. Fixes golang/go#42410 Change-Id: If11ebe6df3bad88aac40b0a6f841edc5fb3a5b4a Reviewed-on: https://go-review.googlesource.com/c/build/+/267937 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-11-02 23:11:10 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-clang": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Container with clang.",
ContainerImage: "linux-x86-clang:latest",
SSHUsername: "root",
dashboard: increase timeout scale for longtest builders, add more CPU Updates golang/go#25886 Change-Id: I5168e291ab77cbd3843bdc39e319a68dfa65aedd Reviewed-on: https://go-review.googlesource.com/c/build/+/167638 Reviewed-by: Russ Cox <rsc@golang.org>
2019-03-14 19:06:57 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-fedora": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Fedora 30",
ContainerImage: "linux-x86-fedora:latest",
SSHUsername: "root",
dashboard, buildlet: add a disabled builder with nested virt, for testing This adds a linux-amd64 COS builder that should be just like our existing linux-amd64 COS builder except that it's using a forked image that has the VMX license bit enabled for nested virtualization. (GCE appears to be using the license mechanism as some sort of opt-in mechanism for features that aren't yet GA; might go away?) Once this is in, it won't do any new builds as regular+trybot builders are disabled. But it means I can then use gomote + debugnewvm to work on preparing the other four image types. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ic55f17eea17908dba7f58618d8cd162a2ed9b015 Reviewed-on: https://go-review.googlesource.com/c/162959 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-16 01:05:42 +03:00
},
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
"host-linux-amd64-js-wasm": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Container with node.js for testing js/wasm.",
ContainerImage: "js-wasm:latest",
SSHUsername: "root",
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-localdev": {
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
IsReverse: true,
ExpectNum: 0,
Notes: "for localhost development of buildlets/gomote/coordinator only",
SSHUsername: os.Getenv("USER"),
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-perf": {
Notes: "Cascade Lake performance testing machines",
dashboard: revert perf builder back to c2-standard-8 CL 419077 changed the perf builder from c2-standard-8 to c2-standard-16. This is not desirable for two reasons: 1. It changed the names of many of our benchmarks (e.g., ZapJSON-8 -> ZapJSON-16), breaking our dashboards. 2. More importantly, this change is almost certain to change performance characteristics which we are trying to keep consistent between runs. Change-Id: If6a283ef02e0b7fed170e17d01930302d72e79b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/420798 Reviewed-by: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com>
2022-08-03 17:58:24 +03:00
machineType: "c2-standard-8", // C2 has precisely defined, consistent server architecture.
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
ContainerImage: "linux-x86-bullseye:latest",
SSHUsername: "root",
CustomDeleteTimeout: 8 * time.Hour,
},
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
"host-linux-amd64-s390x-cross": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Container with s390x cross-compiler.",
ContainerImage: "linux-s390x-cross:latest",
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-sid": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian sid, updated occasionally.",
ContainerImage: "linux-x86-sid:latest",
SSHUsername: "root",
env/js-wasm, dashboard: add start of a js-wasm builder Updates golang/go#18892 Change-Id: I4b16afe8f0ce74f6ecd022f8bca14ada94ab308f Reviewed-on: https://go-review.googlesource.com/112736 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-11 08:54:32 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-stretch": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian Stretch",
ContainerImage: "linux-x86-stretch:latest",
SSHUsername: "root",
env: add alpine linux builder Adds flag to upload to build binary statically. Updates golang/go#17891 Change-Id: If19b2e2cf9a84fa2b4cc6fdf55d8add5b54abff7 Reviewed-on: https://go-review.googlesource.com/33890 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-12-02 22:14:12 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-amd64-wsl": {
Notes: "Windows 10 WSL2 Ubuntu",
Owners: []*gophers.Person{gh("mengzhuo")},
IsReverse: true,
ExpectNum: 2,
},
"host-linux-arm-aws": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian Buster, EC2 arm instance. See x/build/env/linux-arm/aws",
VMImage: "ami-07409163bccd5ac4d",
ContainerImage: "gobuilder-arm-aws:latest",
machineType: "m6g.xlarge",
isEC2: true,
SSHUsername: "root",
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-arm64-aws": {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
Notes: "Debian Buster, EC2 arm64 instance. See x/build/env/linux-arm64/aws",
VMImage: "ami-03089323a1d38e652",
ContainerImage: "gobuilder-arm64-aws:latest",
machineType: "m6g.xlarge",
isEC2: true,
SSHUsername: "root",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
"host-linux-arm64-bullseye": {
Notes: "Debian Bullseye",
ContainerImage: "linux-arm64-bullseye:latest",
machineType: "t2a",
SSHUsername: "root",
cosArchitecture: CosArchARM64,
},
all: add additional storage to linux-arm64-longtest builder This adds the ability to set the size of the root drive for a GCE host machine. The linux-arm64-longtest boot disk has been increased from 10GB to 20GB. Updates golang/go#49649 Change-Id: I74ebf4bd533c91c8716b7df167afacbfdded3ed3 Reviewed-on: https://go-review.googlesource.com/c/build/+/453955 Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-29 19:51:40 +03:00
"host-linux-arm64-bullseye-high-disk": {
Notes: "Debian Bullseye, larger boot disk size",
ContainerImage: "linux-arm64-bullseye:latest",
machineType: "t2a",
SSHUsername: "root",
cosArchitecture: CosArchARM64,
RootDriveSizeGB: 20,
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-loong64-3a5000": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
Notes: "Loongson 3A5000 Box hosted by Loongson; loong64 is the short name of LoongArch 64 bit version",
dashboard: update host-linux-loong64-3a5000 owner, ExpectNum, bootstrap For golang/go#46229 Change-Id: I817d6af1735fb5ca659d4537d401e93ce8e08df0 Reviewed-on: https://go-review.googlesource.com/c/build/+/453457 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: xiaodong liu <teaofmoli@gmail.com>
2022-11-29 02:45:41 +03:00
Owners: []*gophers.Person{gh("XiaodongLoong"), gh("abner-chenc")},
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
IsReverse: true,
dashboard: update host-linux-loong64-3a5000 owner, ExpectNum, bootstrap For golang/go#46229 Change-Id: I817d6af1735fb5ca659d4537d401e93ce8e08df0 Reviewed-on: https://go-review.googlesource.com/c/build/+/453457 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: xiaodong liu <teaofmoli@gmail.com>
2022-11-29 02:45:41 +03:00
ExpectNum: 5,
GoBootstrap: "none",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
env: []string{
dashboard: update host-linux-loong64-3a5000 owner, ExpectNum, bootstrap For golang/go#46229 Change-Id: I817d6af1735fb5ca659d4537d401e93ce8e08df0 Reviewed-on: https://go-review.googlesource.com/c/build/+/453457 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: xiaodong liu <teaofmoli@gmail.com>
2022-11-29 02:45:41 +03:00
"GOROOT_BOOTSTRAP=/usr/lib/go-linux-loong64-bootstrap",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
},
"host-linux-mips64-rtrk": {
Notes: "cavium,rhino_utm8 board hosted at RT-RK.com; quad-core cpu, 8GB of ram and 240GB ssd disks.",
Owners: []*gophers.Person{gh("draganmladjenovic")}, // See https://github.com/golang/go/issues/53574#issuecomment-1169891255.
IsReverse: true,
ExpectNum: 1,
},
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
"host-linux-mips64le-rtrk": {
Notes: "cavium,rhino_utm8 board hosted at RT-RK.com; quad-core cpu, 8GB of ram and 240GB ssd disks.",
Owners: []*gophers.Person{gh("draganmladjenovic")}, // See https://github.com/golang/go/issues/53574#issuecomment-1169891255.
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
IsReverse: true,
ExpectNum: 1,
},
all: remove linux-ppc64-osuosl builder Remove the hooks from cmd/coordinator and cmd/buildlet/stage0 too. Also, remove related files from env/linux-ppc64/osuosl. The scripts used for this builder are unique to it. A new set of files should be added for the linux-ppc64-sid builder. Resolve related TODO's. The replacement builder, linux-ppc64-sid, will retain it's current name. Likewise, it is running containers isolated from the host rootfs, update the HermeticReverse setting. Fixes golang/go#55975 Change-Id: I97b6c8c3316960c9e07f500591738352f6a51a0a Reviewed-on: https://go-review.googlesource.com/c/build/+/438535 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com> Reviewed-by: Than McIntosh <thanm@google.com>
2022-10-04 16:54:05 +03:00
"host-linux-ppc64-sid": {
build/dashboard: add linux-ppc64-sid for testing/upgrade new builder for testing OS upgrade Change-Id: I54b7ace3fbfa6805d7d885fd649efedcd68b01c9 Reviewed-on: https://go-review.googlesource.com/c/build/+/426234 Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Paul Murphy <murp@ibm.com>
2022-08-28 05:20:20 +03:00
Notes: "Debian sid; run by Go team on osuosl.org",
dashboard, env/linux-ppc64/osuosl: add documentation for linux-ppc64-sid This replaces the linux-ppc64-osuosl builder in all but name. debian sid has very minimal maintenance for ppc64, thus we need to make a few surgical modification to build and use the docker packages. I've tried to leave enough breadcrumbs to help the next person who needs to update this builder. Change-Id: Ic70341d38126716477cc28afbbd76a34ac43cff4 Reviewed-on: https://go-review.googlesource.com/c/build/+/438795 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com>
2022-10-05 01:05:03 +03:00
Owners: []*gophers.Person{gh("pmur")},
build/dashboard: add linux-ppc64-sid for testing/upgrade new builder for testing OS upgrade Change-Id: I54b7ace3fbfa6805d7d885fd649efedcd68b01c9 Reviewed-on: https://go-review.googlesource.com/c/build/+/426234 Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Paul Murphy <murp@ibm.com>
2022-08-28 05:20:20 +03:00
IsReverse: true,
ExpectNum: 5,
SSHUsername: "root",
all: remove linux-ppc64-osuosl builder Remove the hooks from cmd/coordinator and cmd/buildlet/stage0 too. Also, remove related files from env/linux-ppc64/osuosl. The scripts used for this builder are unique to it. A new set of files should be added for the linux-ppc64-sid builder. Resolve related TODO's. The replacement builder, linux-ppc64-sid, will retain it's current name. Likewise, it is running containers isolated from the host rootfs, update the HermeticReverse setting. Fixes golang/go#55975 Change-Id: I97b6c8c3316960c9e07f500591738352f6a51a0a Reviewed-on: https://go-review.googlesource.com/c/build/+/438535 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com> Reviewed-by: Than McIntosh <thanm@google.com>
2022-10-04 16:54:05 +03:00
HermeticReverse: true,
build/dashboard: add linux-ppc64-sid for testing/upgrade new builder for testing OS upgrade Change-Id: I54b7ace3fbfa6805d7d885fd649efedcd68b01c9 Reviewed-on: https://go-review.googlesource.com/c/build/+/426234 Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Paul Murphy <murp@ibm.com>
2022-08-28 05:20:20 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-ppc64le-osu": {
dashboard, env/linux-ppc64le/osuosl: update notes The VM's have had more resources allocated, and been updated to use an Ubuntu 20.04 base and container image. Also, update the related notes/ownership on the dashboard. Change-Id: Ibc227446e1950366933d937de6a9a9bf44d34532 Reviewed-on: https://go-review.googlesource.com/c/build/+/439675 Reviewed-by: Lynn Boger <laboger@linux.vnet.ibm.com> Reviewed-by: Than McIntosh <thanm@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-05 01:25:44 +03:00
Notes: "Ubuntu 20.04; run by Go team on osuosl.org; see x/build/env/linux-ppc64le/osuosl",
Owners: []*gophers.Person{gh("pmur")},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
IsReverse: true,
ExpectNum: 5,
SSHUsername: "root",
HermeticReverse: true,
},
all: add linux-ppc64le-power10-osu builder This builder requires a patched bootstrap toolchain to accept GOPPC64=power10. Likewise, this folds in a change to update the container images to ubuntu 20.04. This is and has been running on the existing ppc64le builders for a couple months already. Change-Id: Ia86cb711c99c0d8ab5f9de0ae50129fe11e6ccab Reviewed-on: https://go-review.googlesource.com/c/build/+/454515 Run-TryBot: Paul Murphy <murp@ibm.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org>
2022-12-01 01:50:25 +03:00
"host-linux-ppc64le-power10-osu": {
Notes: "Ubuntu 20.04; run by Go team on osuosl.org; see x/build/env/linux-ppc64le/osuosl",
Owners: []*gophers.Person{gh("pmur")},
IsReverse: true,
// GOPPC64=power10 is only supported in go1.20 and later. The container provides a patched boostrap compiler.
env: []string{
"GOPPC64=power10",
"GOROOT_BOOTSTRAP=/usr/local/go-bootstrap"},
SSHUsername: "root",
HermeticReverse: true,
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-ppc64le-power9-osu": {
dashboard, env/linux-ppc64le/osuosl: update notes The VM's have had more resources allocated, and been updated to use an Ubuntu 20.04 base and container image. Also, update the related notes/ownership on the dashboard. Change-Id: Ibc227446e1950366933d937de6a9a9bf44d34532 Reviewed-on: https://go-review.googlesource.com/c/build/+/439675 Reviewed-by: Lynn Boger <laboger@linux.vnet.ibm.com> Reviewed-by: Than McIntosh <thanm@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-05 01:25:44 +03:00
Notes: "Ubuntu 20.04; run by Go team on osuosl.org; see x/build/env/linux-ppc64le/osuosl",
Owners: []*gophers.Person{gh("pmur")},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
IsReverse: true,
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
env: []string{"GOPPC64=power9"},
dashboard, env, cmd/buildlet/testssh: fix gomote ssh for a number of buidlers And add a testssh tool to validate that SSH is working. Updates golang/go#32430 Change-Id: I5182419fa4db31b598f7a02412fb4ecc4060a796 Reviewed-on: https://go-review.googlesource.com/c/build/+/207459 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-15 23:31:23 +03:00
SSHUsername: "root",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
HermeticReverse: true,
env/linux-x86-fedora: add Fedora builder Not using a Fedora kernel yet, but better than nothing. Updates golang/go#26796 Change-Id: I228442bf6606696407a8d3fbd098df59df7353e1 Reviewed-on: https://go-review.googlesource.com/c/build/+/175999 Reviewed-by: Ian Lance Taylor <iant@golang.org>
2019-05-08 19:25:38 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-riscv64-joelsing": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Notes: "SiFive HiFive Unleashed RISC-V board. 8 GB RAM, 4 cores.",
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("4a6f656c")},
dashboard: add linux-riscv64-jsing builder (reverse) Also use this as the riscv64 slowbot, since linux-riscv64-unleashed has been MIA for quite some time. For golang/go#27532 Change-Id: I01309a66b96d4c35dbc9d1e08f55f5357b0acba0 Reviewed-on: https://go-review.googlesource.com/c/build/+/257917 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-09-27 21:25:41 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-riscv64-unmatched": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Notes: "SiFive HiFive Unmatched RISC-V board. 16 GB RAM, 4 cores.",
IsReverse: true,
dashboard: add one more builder for riscv64 unmatched Thanks to PLCT lab(https://plctlab.github.io) contributed an unmatched builder. Change-Id: I68e226edcde9a67de69aaa2599380f14c5dad526 Reviewed-on: https://go-review.googlesource.com/c/build/+/406847 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Zhuo Meng <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-05-18 07:44:07 +03:00
ExpectNum: 2,
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Owners: []*gophers.Person{gh("mengzhuo")},
dashboard: add linux-riscv64-unmatched This adds a reverse buildlet for linux riscv64 running under Hifive Unmatched. For golang/go#46804. Change-Id: If5ed8b47205cecebcb90a4d1b03c463e1eb466c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/329489 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-27 07:26:14 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-linux-s390x": {
Notes: "run by IBM",
dashboard: update Owners for host-linux-s390x Change-Id: I567692a55cd8504badd8100765ce67e3e4f3dad8 Reviewed-on: https://go-review.googlesource.com/c/build/+/442777 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Joedian Reid <joedian@golang.org>
2022-10-13 17:07:25 +03:00
Owners: []*gophers.Person{gh("Vishwanatha-HD"), gh("srinivas-pokala")},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
IsReverse: true,
ExpectNum: 2, // See https://github.com/golang/go/issues/49557#issuecomment-969148789.
},
dashboard: add NetBSD 9.3 builders This adds the 9.3 builders created by running the make file and manually uploading and creating the VM images. Updates golang/go#54773 Change-Id: I0826b1fea1c486ec7cb34abad539672bddc39bb7 Reviewed-on: https://go-review.googlesource.com/c/build/+/450235 Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Joedian Reid <joedian@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-11-14 19:11:34 +03:00
"host-netbsd-386-9_3": {
VMImage: "netbsd-i386-9-3-202211120320",
Notes: "NetBSD 9.3; GCE VM is built from script in build/env/netbsd-386",
machineType: "n2", // force Intel; see go.dev/issue/49209
SSHUsername: "root",
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
},
"host-netbsd-amd64-9_3": {
VMImage: "netbsd-amd64-9-3-202211120320v2",
Notes: "NetBSD 9.3; GCE VM is built from script in build/env/netbsd-amd64",
machineType: "n2", // force Intel; see go.dev/issue/49209
SSHUsername: "root",
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-netbsd-arm-bsiegert": {
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("bsiegert")},
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-netbsd-arm64-bsiegert": {
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("bsiegert")},
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add OpenBSD 6.8 builders This change builds on top of CL 268297, using the updated env script to build OpenBSD 6.8 images, and adding new builders that use them. This has been tested with cmd/debugnewvm on a recent Go tip commit, as well as Go 1.15.4 and 1.14.11 commits. It passed, although there were also some failures seen. Once the builder is added, we'll know the test results for a wider set of commits, and can decide how to proceed from there. Minimize the configuration to a bare minimum. Specifically, remove MinCPUPlatform since setting it "Intel Skylake" was found not to have a noticeable effect on the speed of the build compared to the zero value: # With MinCPUPlatform = "Intel Skylake": $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 17m8.308s # With a zero MinCPUPlatform value: $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 16m28.518s For golang/go#35712. Updates golang/go#42426. Change-Id: I517a85738a034a3a4074488ccecd4408a91a4a07 Reviewed-on: https://go-review.googlesource.com/c/build/+/269577 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-12 20:27:32 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-386-68": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "openbsd-386-68-v3", // v3 adds 009_exit syspatch; see go.dev/cl/278732.
machineType: "n2", // force Intel; see go.dev/issue/49209
Notes: "OpenBSD 6.8 (with 009_exit syspatch); GCE VM, built from build/env/openbsd-386",
SSHUsername: "gopher",
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add OpenBSD 6.8 builders This change builds on top of CL 268297, using the updated env script to build OpenBSD 6.8 images, and adding new builders that use them. This has been tested with cmd/debugnewvm on a recent Go tip commit, as well as Go 1.15.4 and 1.14.11 commits. It passed, although there were also some failures seen. Once the builder is added, we'll know the test results for a wider set of commits, and can decide how to proceed from there. Minimize the configuration to a bare minimum. Specifically, remove MinCPUPlatform since setting it "Intel Skylake" was found not to have a noticeable effect on the speed of the build compared to the zero value: # With MinCPUPlatform = "Intel Skylake": $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 17m8.308s # With a zero MinCPUPlatform value: $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 16m28.518s For golang/go#35712. Updates golang/go#42426. Change-Id: I517a85738a034a3a4074488ccecd4408a91a4a07 Reviewed-on: https://go-review.googlesource.com/c/build/+/269577 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-12 20:27:32 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-386-70": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "openbsd-386-70",
machineType: "n2", // force Intel; see go.dev/issue/49209
Notes: "OpenBSD 7.0; GCE VM, built from build/env/openbsd-386",
SSHUsername: "gopher",
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add n2 and n2d hosts for OpenBSD and NetBSD We recently migrated in CL 354757 from n1 to e2 hosts around the same time issues started appearing with these builders. n1 hosts are notably different in that they are older generation CPUs with hyperthreading disabled. e2 hosts may sometimes be AMD CPUs. n2d hosts are always AMD, so this helps bisect the problem. n2 hosts are always Intel. For golang/go#49209 Change-Id: I60334b44e192b0b95293891b380f2a89227b9235 Reviewed-on: https://go-review.googlesource.com/c/build/+/367534 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-29 19:15:30 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-386-70-n2d": {
dashboard: clean up builders affected by memory corruption Remove freebsd 12.2, which is replaced by 12.3 with the XSAVE fix. Move freebsd 11.* to N2 machines, which are not affected. Remove openbsd and netbsd e2/n1/n2/n2d-specific configurations now that we have mostly understood the nature of that problem. Keep one around so that the runtime team can create gomotes. Move the "official" builder to the n2 cpu that works. For golang/go#49967, golang/go#49209, golang/go#40561. Fixes golang/go#50496. Change-Id: If6989317f06cbec95d5addb19d9e968aecfa3f8a Reviewed-on: https://go-review.googlesource.com/c/build/+/377474 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-10 23:09:53 +03:00
// This host config is only for the runtime team to use investigating golang/go#49209.
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "openbsd-386-70",
machineType: "n2d", // force AMD; see go.dev/issue/49209
Notes: "OpenBSD 7.0; GCE VM, built from build/env/openbsd-386; AMD",
SSHUsername: "gopher",
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add n2 and n2d hosts for OpenBSD and NetBSD We recently migrated in CL 354757 from n1 to e2 hosts around the same time issues started appearing with these builders. n1 hosts are notably different in that they are older generation CPUs with hyperthreading disabled. e2 hosts may sometimes be AMD CPUs. n2d hosts are always AMD, so this helps bisect the problem. n2 hosts are always Intel. For golang/go#49209 Change-Id: I60334b44e192b0b95293891b380f2a89227b9235 Reviewed-on: https://go-review.googlesource.com/c/build/+/367534 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-29 19:15:30 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-amd64-68": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "openbsd-amd64-68-v3", // v3 adds 009_exit syspatch; see go.dev/cl/278732.
machineType: "n2", // force Intel; see go.dev/issue/49209
Notes: "OpenBSD 6.8 (with 009_exit syspatch); GCE VM, built from build/env/openbsd-amd64",
SSHUsername: "gopher",
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard, cmd/release: remove what's unused as of Go 1.16 release We can drop the 32-bit and 10.11 macOS builders, they're unused. Remove FreeBSD 11.1 builder, it's unused. Update freebsd-amd64-race to use the latest available FreeBSD builder. Simplify build policy and comments, removing anything that mentioned Go version 1.14 or older, since they're not relevant anymore. Drop Go 1.14 support from minSupportedMacOSVersion, and add support for the future Go 1.17 release, which will increase minimum macOS version requirement to macOS 10.13. Fixes golang/go#40562. Change-Id: I7beeec0952a516afe99a5154b22c7f25ceeb3da1 Reviewed-on: https://go-review.googlesource.com/c/build/+/293771 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-02-19 20:17:28 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-amd64-70": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "openbsd-amd64-70",
machineType: "n2", // force Intel; see go.dev/issue/49209
Notes: "OpenBSD 7.0; GCE VM, built from build/env/openbsd-amd64",
SSHUsername: "gopher",
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add netbsd-arm-bsiegert This seems to be the last builder still using the old builder binary and not buildlet. It needs an entry in here to switch to buildlet and stage0. Change-Id: If2fdd2298ab88d56b6850061050caf27ca7c8983 Reviewed-on: https://go-review.googlesource.com/c/build/+/168061 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-03-19 16:28:04 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-arm-joelsing": {
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("4a6f656c")},
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-arm64-joelsing": {
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("4a6f656c")},
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-openbsd-mips64-joelsing": {
dashboard: update netbsd, openbsd builders to Go 1.19.2 The NetBSD builders are failing in a way that only manifests with Go 1.17. The OpenBSD builders are also very flaky. Update both operating systems to Go 1.19.2 in hopes of eliminating those flakes. For golang/go#42422. Change-Id: I10a736c12b38924f6fed5269c2cde21c16de4887 Reviewed-on: https://go-review.googlesource.com/c/build/+/442787 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-14 00:12:51 +03:00
IsReverse: true,
ExpectNum: 1,
Owners: []*gophers.Person{gh("4a6f656c")},
GoBootstrap: "go1.19.2", // Go 1.17 is too old; see go.dev/issue/42422
dashboard: add FreeBSD arm64 builder Updates golang/go#24715 Change-Id: I8eb3f6372d69718b6f453e5415cdf16aa00ccae6 Reviewed-on: https://go-review.googlesource.com/c/build/+/198597 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-03 15:56:19 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-plan9-386-0intro": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
IsReverse: true,
ExpectNum: 1,
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
Notes: "QEMU VM, Plan 9 from Bell Labs",
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Owners: []*gophers.Person{gh("0intro")},
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-plan9-386-gce": {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
VMImage: "plan9-386-v7",
Notes: "Plan 9 from 0intro; GCE VM, built from build/env/plan9-386",
env: []string{"GO_TEST_TIMEOUT_SCALE=3"},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
},
"host-plan9-amd64-0intro": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
IsReverse: true,
ExpectNum: 1,
Notes: "QEMU VM, Plan 9 from Bell Labs, 9k kernel",
Owners: []*gophers.Person{gh("0intro")},
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-plan9-arm-0intro": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
IsReverse: true,
ExpectNum: 1,
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
Notes: "Raspberry Pi 3 Model B, Plan 9 from Bell Labs",
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Owners: []*gophers.Person{gh("0intro")},
dashboard: add plan9-386-0intro builder This change adds the plan9-386-0intro builder configuration. Updates golang/go#29801. Change-Id: I5f64f4592a499eb1691498805fd0dfa5082c33d5 Reviewed-on: https://go-review.googlesource.com/c/build/+/175901 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-09 19:52:40 +03:00
},
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
"host-solaris-oracle-amd64-oraclerel": {
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
Notes: "Oracle Solaris amd64 Release System",
dashboard: set HostArch for host-solaris-oracle-amd64-oraclerel Without an explicit HostArch set, this host name leads to "oracle" being inferred as the GOARCH value, while in reality it is "amd64". For golang/go#44505. Change-Id: If3df135d75fae36d9f2fd55ef7f3ba140ecb609f Reviewed-on: https://go-review.googlesource.com/c/build/+/421456 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-05 01:12:22 +03:00
HostArch: "solaris-amd64",
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
Owners: []*gophers.Person{gh("rorth")}, // https://github.com/golang/go/issues/15581#issuecomment-550368581
IsReverse: true,
ExpectNum: 1,
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-windows-amd64-2008": {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
VMImage: "windows-amd64-server-2008r2-v8",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: upsize machine type for windows-amd64-{longtest,race} builders Start using n1-highcpu-8 machine type instead of n1-highcpu-4 for windows-amd64-longtest and windows-amd64-race builders. Continue to use the existing n1-highcpu-4 machine type for all other windows/386 and windows/amd64 builders for now. The primary motivation of this change is to increase amount of RAM available on the longtest builder from 3.6 GB to 7.2 GB, because it is consistenly failing due to being out of memory. Also fix minor typos, and increase consistency in comments and notes. Updates golang/go#33951 Change-Id: Iac5da67fa584059842850a9c8deda98c242741f2 Reviewed-on: https://go-review.googlesource.com/c/build/+/208500 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2019-11-23 02:01:25 +03:00
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
"host-windows-amd64-2008-oldcc": {
VMImage: "windows-amd64-server-2008r2-v7",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-windows-amd64-2012": {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
VMImage: "windows-amd64-server-2012r2-v8",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
"host-windows-amd64-2012-oldcc": {
VMImage: "windows-amd64-server-2012r2-v7",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-windows-amd64-2016": {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
VMImage: "windows-amd64-server-2016-v8",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: upsize machine type for windows-amd64-{longtest,race} builders Start using n1-highcpu-8 machine type instead of n1-highcpu-4 for windows-amd64-longtest and windows-amd64-race builders. Continue to use the existing n1-highcpu-4 machine type for all other windows/386 and windows/amd64 builders for now. The primary motivation of this change is to increase amount of RAM available on the longtest builder from 3.6 GB to 7.2 GB, because it is consistenly failing due to being out of memory. Also fix minor typos, and increase consistency in comments and notes. Updates golang/go#33951 Change-Id: Iac5da67fa584059842850a9c8deda98c242741f2 Reviewed-on: https://go-review.googlesource.com/c/build/+/208500 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2019-11-23 02:01:25 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-windows-amd64-2016-big": {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
VMImage: "windows-amd64-server-2016-v8",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
machineType: "e2-standard-16",
SSHUsername: "gopher",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
"host-windows-amd64-2016-big-oldcc": {
VMImage: "windows-amd64-server-2016-v7",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
machineType: "e2-standard-16",
SSHUsername: "gopher",
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
"host-windows-amd64-2016-oldcc": {
VMImage: "windows-amd64-server-2016-v7",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
SSHUsername: "gopher",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
},
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
"host-windows-arm64-mini": { // host name known to cmd/buildlet/stage0, cannot change
internal/releasetargets: add hosting information to releases.txt Add a line describing the hosting environment of each release builder. I didn't include long test builder information; the long test builders run in the same environment as the normal ones. Change-Id: I47118ff36243b04933258c843a466625d44ad222 Reviewed-on: https://go-review.googlesource.com/c/build/+/423995 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-08-15 22:30:41 +03:00
Notes: "MacStadium mac minis hosting Windows 10 in qemu with HVM acceleration.",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
IsReverse: true,
ExpectNum: 2,
all: add Windows 11 builder Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-12 01:15:28 +03:00
},
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
"host-windows-arm64-zx2c4": {
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
IsReverse: true,
dashboard: sort hosts table It is easier to find entries if the table is sorted. Change-Id: I1f13ab081c85055e139a2ddb2f849fcf196d0fd0 Reviewed-on: https://go-review.googlesource.com/c/build/+/419985 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: David Chase <drchase@google.com> Auto-Submit: Russ Cox <rsc@golang.org>
2022-07-26 19:05:33 +03:00
ExpectNum: 0,
Owners: []*gophers.Person{gh("zx2c4")},
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
},
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
"host-windows11-arm64-mini": { // host name known to cmd/buildlet/stage0, cannot change
internal/releasetargets: add hosting information to releases.txt Add a line describing the hosting environment of each release builder. I didn't include long test builder information; the long test builders run in the same environment as the normal ones. Change-Id: I47118ff36243b04933258c843a466625d44ad222 Reviewed-on: https://go-review.googlesource.com/c/build/+/423995 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-08-15 22:30:41 +03:00
Notes: "MacStadium mac minis hosting Windows 11 in qemu with HVM acceleration.",
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
HostArch: "windows-arm64",
IsReverse: true,
ExpectNum: 5,
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
},
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
}
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
func gh(githubUsername string) *gophers.Person {
p := gophers.GetPerson("@" + githubUsername)
if p == nil {
panic("person with GitHub username " + githubUsername + " does not exist in the golang.org/x/build/internal/gophers package")
}
return p
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
func init() {
for key, c := range Hosts {
if key == "" {
panic("empty string key in Hosts")
}
if c.HostType == "" {
c.HostType = key
}
if c.HostType != key {
panic(fmt.Sprintf("HostType %q != key %q", c.HostType, key))
}
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
if c.HostArch == "" {
f := strings.Split(c.HostType, "-")
if len(f) < 3 {
panic(fmt.Sprintf("invalid HostType %q", c.HostType))
}
c.HostArch = f[1] + "-" + f[2] // "linux-amd64"
if f[2] == "arm" {
c.HostArch += "-7" // assume newer ARM
}
}
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
if c.GoBootstrap == "" {
c.GoBootstrap = GoBootstrap
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
nSet := 0
dashboard: add windows-arm64 builder Add the windows-arm64 builder to the dashboard and coordinator with a known issue until we can verify builds are succeeding regularly. Also, tweak the logic around validating ec2 configurations. The arm64 buildlet sets VMImage but not ContainerImage, unlike other ec2 buildlets. This should work for both. For golang/go#42604 Change-Id: I7176b8f6bba837830a0565e7713c9e9a0eb76e90 Reviewed-on: https://go-review.googlesource.com/c/build/+/322656 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-05-26 04:47:41 +03:00
if c.VMImage != "" {
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
nSet++
}
dashboard: add windows-arm64 builder Add the windows-arm64 builder to the dashboard and coordinator with a known issue until we can verify builds are succeeding regularly. Also, tweak the logic around validating ec2 configurations. The arm64 buildlet sets VMImage but not ContainerImage, unlike other ec2 buildlets. This should work for both. For golang/go#42604 Change-Id: I7176b8f6bba837830a0565e7713c9e9a0eb76e90 Reviewed-on: https://go-review.googlesource.com/c/build/+/322656 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-05-26 04:47:41 +03:00
if c.ContainerImage != "" && !c.isEC2 {
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
nSet++
}
if c.IsReverse {
nSet++
}
if nSet != 1 {
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
panic(fmt.Sprintf("exactly one of VMImage, ContainerImage, IsReverse must be set for host %q; got %v", key, nSet))
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
}
}
}
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
// CosArch defines the diffrent COS images types used.
type CosArch string
const (
CosArchAMD64 CosArch = "cos-stable" // COS image for AMD64 architecture
CosArchARM64 = "cos-arm64-stable" // COS image for ARM64 architecture
)
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
// A HostConfig describes the available ways to obtain buildlets of
dashboard, app/appengine: set a known issue for staticlockranking builder The linux-amd64-staticlockranking builder was added pre-emptively so that it could be tested and used during the development of a CL that implements a new feature. It's expected to fail until that work is completed. Mark it as a builder with a known issue, golang/go#38029. The new BuildConfig.KnownIssue field can be used by builders being added in the future so that if they fail at first, it doesn't take away time for people looking at build.golang.org, which we always aim to have as green as possible¹. ¹ https://groups.google.com/d/msg/golang-dev/y0yM_Xi665Q/hUpBiUPiCAAJ Fixes golang/go#38283 For golang/go#38029 For golang/go#37937 For golang/go#11811 Change-Id: Iba1606c7021ffa7e67ddbaae2fc6b65f4e46ab34 Reviewed-on: https://go-review.googlesource.com/c/build/+/227379 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-07 00:34:17 +03:00
// different types. Some host configs can serve multiple
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
// builders. For example, a host config of "host-linux-amd64-bullseye" can
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
// serve linux-amd64, linux-amd64-race, linux-386, linux-386-387, etc.
type HostConfig struct {
// HostType is the unique name of this host config. It is also
// the key in the Hosts map.
HostType string
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
// HostArch is a string identifying the host architecture, to decide which binaries to run on it.
// If unset, it is derived in func init from the HostType
// (for example, host-linux-amd64-foo has HostArch "linux-amd64").
// For clarity, the HostArch for 32-bit arm always ends in -5 or -7
// to specify the GOARM value; implicit HostArch always use -7.
// (This specificity is necessary because there is no one value that
// works on all 32-bit ARM chips on non-Linux operating systems.)
//
// If set explicitly, HostArch should have the form "GOOS-GOARCH-suffix",
// where suffix is the GO$GOARCH setting (that is, GOARM for GOARCH=arm).
// For example "openbsd-arm-5" for GOOS=openbsd GOARCH=arm GOARM=5.
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
//
// (See the BuildletBinaryURL and GoBootstrapURL methods.)
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
HostArch string
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
// GoBootstrap is the version of Go to use for bootstrap.
// A bootstrap toolchain built with that version must be in the bucket.
// If unset, it is set in func init to GoBootstrap (the global constant).
//
// If GoBootstrap is set to "none", it means this buildlet is not given a new bootstrap
// toolchain for each build, typically because it cannot download from
// storage.googleapis.com.
//
// (See the GoBootstrapURL method.)
GoBootstrap string
dashboard: add host-linux-arm64-aws builder Add the host-linux-arm64-aws builder. The HostConfig IsVM method has been modified to support the concept that an EC2 VM can be created which runs the buildlet binary in a container. This configuration would have both a VM image and a container image set in the host configuration. For golang/go#36841 Change-Id: I092b48b1dda24d24bcd0b10dff0b2126f5f43017 Reviewed-on: https://go-review.googlesource.com/c/build/+/249118 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-18 20:32:05 +03:00
// Exactly 1 of these must be set (with the exception of EC2 instances).
// An EC2 instance may run a container inside a VM. In that case, a VMImage
// and ContainerImage will both be set.
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
VMImage string // e.g. "openbsd-amd64-60"
ContainerImage string // e.g. "linux-buildlet-std:latest" (suffix after "gcr.io/<PROJ>/")
IsReverse bool // if true, only use the reverse buildlet pool
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
// GCE options, if VMImage != "" || ContainerImage != ""
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
machineType string // optional GCE instance type ("n2-standard-4") or instance class ("n2")
RegularDisk bool // if true, use spinning disk instead of SSD
MinCPUPlatform string // optional. e2 instances are not supported. see https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform.
cosArchitecture CosArch // optional. GCE instances which use COS need the architecture set. Default: CosArchAMD64
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
dashboard, buildenv: label EC2 instances This change adds a boolean which identified when an instance is an EC2 instance. Various EC2 related variables have been renamed to be more consistent. Updates golang/go#36841 Change-Id: Ief385bf9d41e320ebd7d31bc0108e8053f337afd Reviewed-on: https://go-review.googlesource.com/c/build/+/233801 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 20:27:15 +03:00
// EC2 options
isEC2 bool // if true, the instance is configured to run on EC2
cmd/coordinator: consolidate and increase global VM deletion timeout We had a lot of flexibility over timeouts, making their maintenance harder. Consolidate it to a single timeout in the pool package, and modify it from 45 minutes to 2 hours. There's room for improvement in how we maintain this timeout, but I'm leaving that for future work (with a tracking issue). Fixes golang/go#52591. Updates golang/go#52929. Updates golang/go#49666. Updates golang/go#42699. Change-Id: I2ad92648d89a714397bd8b0e1ec490fc9f6d6790 Reviewed-on: https://go-review.googlesource.com/c/build/+/406216 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-05-13 19:08:32 +03:00
// GCE or EC2 options:
//
// CustomDeleteTimeout is an optional custom timeout after which the VM is forcibly destroyed and the build is retried.
// Zero duration defers decision to internal/coordinator/pool package, which is enough for longtest post-submit builds.
// (This is generally an internal implementation detail, currently left behind only for the -perf builder.)
CustomDeleteTimeout time.Duration
dashboard,internal/coordinator/pool: VM delete timeout from host config Allow individual host configurations to override the VM delete timeout if they are using for longer than normal builds. For golang/go#49207. Change-Id: I9c5c80e5ee7dac2375cff17c64871ae2211f6309 Reviewed-on: https://go-review.googlesource.com/c/build/+/378334 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-01-13 19:26:27 +03:00
// Reverse options
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
ExpectNum int // expected number of reverse buildlets of this type
HermeticReverse bool // whether reverse buildlet has fresh env per conn
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
GoogleReverse bool // whether this reverse builder is owned by Google
cmd/coordinator: clean up reverse buildlet code, export status JSON Will be used for dynamic creation/destruction of Mac VMs in subsequent CL. Updates golang/go#9495 (Mac virtualization) Updates golang/go#15760 (monitoring) Change-Id: I48b17589b258d5d742bad5a3ddae18de98778149 Reviewed-on: https://go-review.googlesource.com/37457 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-02-24 20:50:49 +03:00
dashboard, buildlet: add a disabled builder with nested virt, for testing This adds a linux-amd64 COS builder that should be just like our existing linux-amd64 COS builder except that it's using a forked image that has the VMX license bit enabled for nested virtualization. (GCE appears to be using the license mechanism as some sort of opt-in mechanism for features that aren't yet GA; might go away?) Once this is in, it won't do any new builds as regular+trybot builders are disabled. But it means I can then use gomote + debugnewvm to work on preparing the other four image types. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ic55f17eea17908dba7f58618d8cd162a2ed9b015 Reviewed-on: https://go-review.googlesource.com/c/162959 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-16 01:05:42 +03:00
// Container image options, if ContainerImage != "":
dashboard: use n2 instances where necessary e2 and n2d instances do not support specifying a MinCPUVersion or NestedVirt. For golang/go#48969 Change-Id: I0c4b359b29cd24302b869748014f848a9b7b5e39 Reviewed-on: https://go-review.googlesource.com/c/build/+/356071 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-10-15 04:54:32 +03:00
NestedVirt bool // container requires VMX nested virtualization. e2 and n2d instances are not supported.
env/linux-x86-vmx: add new Debian host that's like Container-Optimized OS + vmx This adds scripts to create a new builder host image that acts like Container-Optimized OS (has docker, runs konlet on startup) but with a Debian 9 kernel + userspace that permits KVM for nested virtualization. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ib1d3a250556703856083c222be2a70c4e8d91884 Reviewed-on: https://go-review.googlesource.com/c/163301 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-22 00:10:54 +03:00
KonletVMImage string // optional VM image (containing konlet) to use instead of default
dashboard, buildlet: add a disabled builder with nested virt, for testing This adds a linux-amd64 COS builder that should be just like our existing linux-amd64 COS builder except that it's using a forked image that has the VMX license bit enabled for nested virtualization. (GCE appears to be using the license mechanism as some sort of opt-in mechanism for features that aren't yet GA; might go away?) Once this is in, it won't do any new builds as regular+trybot builders are disabled. But it means I can then use gomote + debugnewvm to work on preparing the other four image types. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ic55f17eea17908dba7f58618d8cd162a2ed9b015 Reviewed-on: https://go-review.googlesource.com/c/162959 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-16 01:05:42 +03:00
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
// Optional base env.
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
env []string
dashboard: rename Go14URL to goBootstrapURLTmpl and provide accessor Also update all users, and rename another template field. Includes changes to coordinator, gomote, and release. Change-Id: I1c4408eadbcb83d61063a910dfa18cc395952bc2 Reviewed-on: https://go-review.googlesource.com/20976 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-03-22 01:05:52 +03:00
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Owners []*gophers.Person // owners; empty means golang-dev
Notes string // notes for humans
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
SSHUsername string // username to ssh as, empty means not supported
all: add additional storage to linux-arm64-longtest builder This adds the ability to set the size of the root drive for a GCE host machine. The linux-arm64-longtest boot disk has been increased from 10GB to 20GB. Updates golang/go#49649 Change-Id: I74ebf4bd533c91c8716b7df167afacbfdded3ed3 Reviewed-on: https://go-review.googlesource.com/c/build/+/453955 Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-29 19:51:40 +03:00
RootDriveSizeGB int64 // optional, GCE instance root size in base-2 GB. Default: default size for instance type.
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
}
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
// CosArchitecture returns the COS architecture to use with the host. The default is CosArchAMD64.
func (hc *HostConfig) CosArchitecture() CosArch {
if hc.cosArchitecture == CosArch("") {
return CosArchAMD64
}
return hc.cosArchitecture
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
// A BuildConfig describes how to run a builder.
type BuildConfig struct {
// Name is the unique name of the builder, in the form of
// "GOOS-GOARCH" or "GOOS-GOARCH-suffix". For example,
// "darwin-386", "linux-386-387", "linux-amd64-race". Some
// suffixes are well-known and carry special meaning, such as
// "-race".
Name string
// HostType is the required key into the Hosts map, describing
// the type of host this build will run on.
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
// For example, "host-linux-amd64-bullseye".
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
HostType string
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// KnownIssues is a slice of non-zero go.dev/issue/nnn numbers for a
dashboard: allow multiple known-issues for builders We may know of more than one issue affecting a builder. In some contexts (such as the build dashboard) we only have enough room to display one of those, but in other contexts (such as SlowBot failure messages) it may be useful to see all of them as a list. Moreover, this way we don't have to remember to check for other known issues when removing an issue that has been resolved. For golang/go#52653. Change-Id: I9da42a3bf99ad24ec4b3ba9c4e6ce214b9f9cac7 Reviewed-on: https://go-review.googlesource.com/c/build/+/408696 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-05-26 18:06:10 +03:00
// builder that may fail due to a known issue, such as because it is a new
dashboard: create misc-compile-ios builder Create the builder as a post-submit builder with a non-zero KnownIssue value first. Once we know it works well, we'll have the confidence to be able to safely promote it to a normal TryBot, without the risk of causing disruption for contributors. For golang/go#41610. Change-Id: If871addf325b7728109afbe094b72d40e27ceec1 Reviewed-on: https://go-review.googlesource.com/c/build/+/257617 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
2020-09-25 18:52:04 +03:00
// builder still in development/testing, or because the feature
dashboard, app/appengine: set a known issue for staticlockranking builder The linux-amd64-staticlockranking builder was added pre-emptively so that it could be tested and used during the development of a CL that implements a new feature. It's expected to fail until that work is completed. Mark it as a builder with a known issue, golang/go#38029. The new BuildConfig.KnownIssue field can be used by builders being added in the future so that if they fail at first, it doesn't take away time for people looking at build.golang.org, which we always aim to have as green as possible¹. ¹ https://groups.google.com/d/msg/golang-dev/y0yM_Xi665Q/hUpBiUPiCAAJ Fixes golang/go#38283 For golang/go#38029 For golang/go#37937 For golang/go#11811 Change-Id: Iba1606c7021ffa7e67ddbaae2fc6b65f4e46ab34 Reviewed-on: https://go-review.googlesource.com/c/build/+/227379 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-07 00:34:17 +03:00
// or port that it's meant to test hasn't been added yet, etc.
//
// A non-zero value here means that failures on this builder should not
// be considered a serious regression and don't need investigation beyond
dashboard: allow multiple known-issues for builders We may know of more than one issue affecting a builder. In some contexts (such as the build dashboard) we only have enough room to display one of those, but in other contexts (such as SlowBot failure messages) it may be useful to see all of them as a list. Moreover, this way we don't have to remember to check for other known issues when removing an issue that has been resolved. For golang/go#52653. Change-Id: I9da42a3bf99ad24ec4b3ba9c4e6ce214b9f9cac7 Reviewed-on: https://go-review.googlesource.com/c/build/+/408696 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-05-26 18:06:10 +03:00
// what is already in scope of the listed issues.
KnownIssues []int
dashboard, app/appengine: set a known issue for staticlockranking builder The linux-amd64-staticlockranking builder was added pre-emptively so that it could be tested and used during the development of a CL that implements a new feature. It's expected to fail until that work is completed. Mark it as a builder with a known issue, golang/go#38029. The new BuildConfig.KnownIssue field can be used by builders being added in the future so that if they fail at first, it doesn't take away time for people looking at build.golang.org, which we always aim to have as green as possible¹. ¹ https://groups.google.com/d/msg/golang-dev/y0yM_Xi665Q/hUpBiUPiCAAJ Fixes golang/go#38283 For golang/go#38029 For golang/go#37937 For golang/go#11811 Change-Id: Iba1606c7021ffa7e67ddbaae2fc6b65f4e46ab34 Reviewed-on: https://go-review.googlesource.com/c/build/+/227379 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-07 00:34:17 +03:00
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
Notes string // notes for humans
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// tryBot optionally specifies a policy func for whether trybots are enabled.
// nil means off. Even if tryBot returns true, BuildConfig.BuildsRepo must also
// return true. See the implementation of BuildConfig.BuildsRepoTryBot.
// The proj is "go", "net", etc. The branch is proj's branch.
// The goBranch is the same as branch for proj "go", else it's the go branch
// ("master, "release-branch.go1.12", etc).
tryBot func(proj, branch, goBranch string) bool
tryOnly bool // only used for trybots, and not regular builds
CompileOnly bool // if true, compile tests, but don't run them
FlakyNet bool // network tests are flaky (try anyway, but ignore some failures)
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// buildsRepo optionally specifies whether this builder does
// builds (of any type) for the given repo ("go", "net", etc.)
// and its branch ("master", "release-branch.go1.12", "dev.link", etc.).
// goBranch is the branch of "go" to build against. If repo == "go",
// goBranch == branch.
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
//
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// If nil, a default set of repos as reported by buildRepoByDefault
// is built. See buildsRepoAtAll method for details.
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
//
// To implement a minor change to the default policy, create a
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// function that uses buildRepoByDefault. For example:
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
//
// buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// b := buildRepoByDefault(repo)
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
// // ... modify b from the default value as needed ...
// return b
// }
//
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
buildsRepo func(repo, branch, goBranch string) bool
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
cmd/coordinator: run performance tests from x/benchmarks Add initial support for running the performance tests from x/benchmarks. Since there are a variety of different test suites (some `go test`, bent, etc), x/benchmarks provides a basic wrapper command, golang.org/x/benchmarks/cmd/bench which know the minute details. The coordinator just needs to run that one command. This build mode is limited to builds of x/benchmarks on builders with RunBench set to true. Currently there are none, a future CL will add the initial such linux-amd64 builder. For golang/go#49207 Change-Id: Ie006ec4a3757a5c2fed0925a3f9eb91edeaa5224 Reviewed-on: https://go-review.googlesource.com/c/build/+/361417 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-11 20:25:58 +03:00
// RunBench enables benchmarking of the toolchain using x/benchmarks.
// This only applies when building x/benchmarks.
RunBench bool
dashboard, cmd/coordinator, maintner/maintnerd: add support for BuildConfig.MinimumGoVersion field The new BuildConfig.MinimumGoVersion field specifies the minimum Go version the builder is allowed to use. It's useful when some of the builders are too new, and do not support all of the supported Go releases (e.g., openbsd-amd64-64 and freebsd-amd64-12_0 currently require Go 1.11 and don't work on Go 1.10). It only needs to be set when a builder doesn't support all supported Go releases, since we don't typically test unsupported Go releases. To allow cmd/coordinator to use this field and filter out work it receives from maintner/maintnerd's GoFindTryWork RPC call, we add a GoVersion slice to apipb.GerritTryWorkItem, and populate it in maintapi.apiService.GoFindTryWork method. For trybots on the Go repo, the GoVersion field is determined from the branch name. For "release-branch.goX.Y" branches, it parses out the major-minor Go version from the branch name. For master and other branches, it assumes the latest Go release. For trybots on subrepos, we already have the Go version information available, so use it directly. Afterwards, all that's left is to modify newTrySet in cmd/coordinator to make use of BuildConfig.MinimumGoVersion and work.GoVersion to skip builders that are too new for the Go version that needs to be tested. Fixes golang/go#29265 Change-Id: I50b01830647e33e37e9eb8b89e0f2518812fa44f Reviewed-on: https://go-review.googlesource.com/c/155463 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-01-12 00:44:01 +03:00
// MinimumGoVersion optionally specifies the minimum Go version
// this builder is allowed to use. It can be useful for skipping
// builders that are too new and no longer support some supported
// Go versions. It doesn't need to be set for builders that support
// all supported Go versions.
//
// Note: This field currently has effect on trybot runs only.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
//
// TODO: unexport this and make buildsRepoAtAll return false on too-old
// of repos. The callers in coordinator will need updating.
dashboard, cmd/coordinator, maintner/maintnerd: add support for BuildConfig.MinimumGoVersion field The new BuildConfig.MinimumGoVersion field specifies the minimum Go version the builder is allowed to use. It's useful when some of the builders are too new, and do not support all of the supported Go releases (e.g., openbsd-amd64-64 and freebsd-amd64-12_0 currently require Go 1.11 and don't work on Go 1.10). It only needs to be set when a builder doesn't support all supported Go releases, since we don't typically test unsupported Go releases. To allow cmd/coordinator to use this field and filter out work it receives from maintner/maintnerd's GoFindTryWork RPC call, we add a GoVersion slice to apipb.GerritTryWorkItem, and populate it in maintapi.apiService.GoFindTryWork method. For trybots on the Go repo, the GoVersion field is determined from the branch name. For "release-branch.goX.Y" branches, it parses out the major-minor Go version from the branch name. For master and other branches, it assumes the latest Go release. For trybots on subrepos, we already have the Go version information available, so use it directly. Afterwards, all that's left is to modify newTrySet in cmd/coordinator to make use of BuildConfig.MinimumGoVersion and work.GoVersion to skip builders that are too new for the Go version that needs to be tested. Fixes golang/go#29265 Change-Id: I50b01830647e33e37e9eb8b89e0f2518812fa44f Reviewed-on: https://go-review.googlesource.com/c/155463 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-01-12 00:44:01 +03:00
MinimumGoVersion types.MajorMinor
dashboard, cmd/coordinator: clean up snapshot code, add snapshot opt-out The snapshot code had an old workaround that's no longer relevant. Remove it. Also, add a BuildConfig.SkipSnapshot bool, and use it for the slow mips builders. Fixes golang/go#19953 Change-Id: I114bb0a524184eaaae5be4715ce63f6adc519c2e Reviewed-on: https://go-review.googlesource.com/40505 Reviewed-by: Sarah Adams <shadams@google.com>
2017-04-13 07:34:42 +03:00
// SkipSnapshot, if true, means to not fetch a tarball
// snapshot of the world post-make.bash from the buildlet (and
// thus to not write it to Google Cloud Storage). This is
// incompatible with sharded tests, and should only be used
// for very slow builders or networks, unable to transfer
// the tarball in under ~5 minutes.
SkipSnapshot bool
dashboard: add a make.bash-only builder on real ARM hardware This is a new builder in prep for the change to the "linux-arm" builder where the GOARCH=arm make.bash will be cross-compiled from a Kubernetes container on fast hardware. Updates golang/go#17105 (cross-compile ARM builders' make.bash) Updates golang/go#17104 (5 minute trybots) Change-Id: Icfd2644d77639f731151abe54839322960418254 Reviewed-on: https://go-review.googlesource.com/29670 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 02:29:31 +03:00
// StopAfterMake causes the build to stop after the make
// script completes, returning its result as the result of the
// whole build. It does not run or compile any of the tests,
// nor does it write a snapshot of the world to cloud
// storage. This option is only supported for builders whose
// BuildConfig.SplitMakeRun returns true.
StopAfterMake bool
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// needsGoProxy is whether this builder should have GOPROXY set.
// Currently this is only for the longtest builder, which needs
// to run cmd/go tests fetching from the network.
needsGoProxy bool
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
// privateGoProxy for builder has it's own Go proxy instead of
// proxy.golang.org, after setting this builder will respect
all: fix some typos Change-Id: Id8468705aa93a615caf014196cc77529bf991a9f GitHub-Last-Rev: 7598fb5831bde8f6b17bfd76462ded972e6eb502 GitHub-Pull-Request: golang/build#46 Reviewed-on: https://go-review.googlesource.com/c/build/+/429455 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Ian Lance Taylor <iant@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com>
2022-09-08 15:03:49 +03:00
// GOPROXY environment value.
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
privateGoProxy bool
dashboard, cmd/coordinator: add -racecompile builder Change-Id: Idc5756f82081de6b5dfd17036f2bfc9cf11c5659 Reviewed-on: https://go-review.googlesource.com/41414 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-22 02:41:12 +03:00
// InstallRacePackages controls which packages to "go install
// -race <pkgs>" after running make.bash (or equivalent). If
// the builder ends in "-race", the default if non-nil is just
// "std".
InstallRacePackages []string
cmd/coordinator: move git ancestor checking before buildlet creation, generalize This also adds GoDeps to the builders config file and adds a dependency for the ssacheck builder, which currently fails on older release branches with: > Failed on linux-amd64-ssacheck: > https://storage.googleapis.com/go-build-log/1255edaf/linux-amd64-ssacheck_18f7e015.log > > ... > compile: unknown debug key -d dclstack Change-Id: I4ad0a298705feed56f467f3c8d9488f8be2e4af5 Reviewed-on: https://go-review.googlesource.com/43774 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-05-20 00:23:14 +03:00
// GoDeps is a list of of git sha1 commits that must be in the
// commit to be tested's history. If absent, this builder is
// not run for that commit.
GoDeps []string
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// distTestAdjust optionally specifies a function that can
// adjust the cmd/dist test policy for this builder.
//
// The BuildConfig.ShouldRunDistTest method implements the
// default cmd/dist test policy, and then calls distTestAdjust
// to adjust that decision further, if distTestAdjust is not nil.
//
// The initial value of the run parameter is what the default
// policy said. The returned value from distTestAdjust is what
// BuildConfig.ShouldRunDistTest reports to the caller.
//
// For example:
//
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
// distTestAdjust: func(run bool, distTest string, isNormalTry bool) bool {
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// // ... modify run from the initial value as needed ...
// return run
// }
//
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
distTestAdjust func(run bool, distTest string, isNormalTry bool) bool
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
// numTestHelpers is the number of _additional_ buildlets
// past the first one to help out with sharded tests.
dashboard: try to speed up pre-submit longtest builders The longtest builders are currently primarily post-submit builders, where it's okay for them to be as slow as they need to be in order to provide additional test coverage. In this context, whether they take 40 minutes or 50 makes little difference. The longtest builders are also sometimes requested via SlowBots for changes that are riskier than usual, or otherwise desire additional coverage beyond the normal TryBots. They're also always enabled for CLs to release branches. In such contexts, speeding up SlowBot runs from 40 minutes to 20 or less would be appreciated and in turn help people use longtest SlowBots more frequently. Longtest builders are already configured to use sharded tests. Configure them to use additional helpers to speed up test execution. Try out 3, 5, and 9 helpers to see how much it helps before settling. For golang/go#37439. Change-Id: I425bc0257b7a54bb32c0eb1719fea7ba3f4fd461 Reviewed-on: https://go-review.googlesource.com/c/build/+/268037 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-06 15:55:36 +03:00
// For TryBots and SlowBots, the numTryHelpers value is used,
// unless it's zero, in which case numTestHelpers is used.
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
numTestHelpers int
dashboard: try to speed up pre-submit longtest builders The longtest builders are currently primarily post-submit builders, where it's okay for them to be as slow as they need to be in order to provide additional test coverage. In this context, whether they take 40 minutes or 50 makes little difference. The longtest builders are also sometimes requested via SlowBots for changes that are riskier than usual, or otherwise desire additional coverage beyond the normal TryBots. They're also always enabled for CLs to release branches. In such contexts, speeding up SlowBot runs from 40 minutes to 20 or less would be appreciated and in turn help people use longtest SlowBots more frequently. Longtest builders are already configured to use sharded tests. Configure them to use additional helpers to speed up test execution. Try out 3, 5, and 9 helpers to see how much it helps before settling. For golang/go#37439. Change-Id: I425bc0257b7a54bb32c0eb1719fea7ba3f4fd461 Reviewed-on: https://go-review.googlesource.com/c/build/+/268037 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-06 15:55:36 +03:00
numTryTestHelpers int // For TryBots/SlowBots. If 0, numTestHelpers is used.
cmd/coordinator: test sharding, better status, logs Also gomote updates which came about during the process of developing and debugging this. Change-Id: Ia53d674118a6b99bcdda7062d3b7161279b6ad52 Reviewed-on: https://go-review.googlesource.com/10463 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-28 07:51:25 +03:00
buildlet, cmd/coordinator: GCE quota accounting, fixes And deal with Preemptible resource exhaustion errors. And change all-compile to misc-compile and only do the builders not covered otherwise (Fixes #11073) And make the watcher serve git source. And cache and singleflight fetching of git source. And a million other things. Fixes golang/go#11073 Change-Id: I0f45610f0c6a06bd0c8ba9632b8624e00aeb52fc Reviewed-on: https://go-review.googlesource.com/10750 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-05 04:25:50 +03:00
env []string // extra environment ("key=value") pairs
allScriptArgs []string
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
testHostConf *HostConfig // override HostConfig for testing, at least for now
dashboard: add privileged flag for builders This change adds a privileged flag for builders. Updates golang/go#47521 Change-Id: Icbc72bc21dd4345da65c2e231f0f59af5dd05ca1 Reviewed-on: https://go-review.googlesource.com/c/build/+/370661 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2021-12-09 22:12:12 +03:00
// isRestricted marks if a builder should be restricted to a subset of users.
isRestricted bool
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// Env returns the environment variables this builder should run with.
cmd/coordinator: set GO_BUILDER_NAME env var when exec'ing on buildlet This will allow tests to identify that they are running on the continuous build infrastructure and run extra and/or different tests. Fixes golang/go#11346 Change-Id: Iafe25babc764b7e012c05f0b62331b11690bf194 Reviewed-on: https://go-review.googlesource.com/13120 Reviewed-by: Russ Cox <rsc@golang.org>
2015-08-04 05:19:02 +03:00
func (c *BuildConfig) Env() []string {
dashboard: mark some builders as having flaky networks Follow-up to https://golang.org/cl/22852 Change-Id: I5f0cd25248a8892b7d1b0f14e87b12b8b9a8da3a Reviewed-on: https://go-review.googlesource.com/22883 Reviewed-by: Ian Lance Taylor <iant@golang.org>
2016-05-06 21:55:26 +03:00
env := []string{"GO_BUILDER_NAME=" + c.Name}
if c.FlakyNet {
env = append(env, "GO_BUILDER_FLAKY_NET=1")
}
dashboard: use a more consistent definition for longtest builders Previously, it was possible to define a builder whose IsLongTest method would report positively, such that it'd test golang.org/x repos in long test mode, but the main Go repository in short test mode. This would be the case for any builder with "-longtest" suffix if it did not manually include GO_TEST_SHORT=0 in its environment configuration. It's unlikely we would want to do that intentionally, so this refactor makes such misconfiguration less likely by inserting the GO_TEST_SHORT environment variable assignment into the output from Env automatically. Now, a longtest builder is defined in one consistent way: it must have a "-longtest" suffix, so that the IsLongTest method reports positively. For golang/go#39054. For golang/go#29252. For golang/go#12508. Change-Id: Ic24df7b3b7de7db728bba6dc6ad4dd38a2e61e82 Reviewed-on: https://go-review.googlesource.com/c/build/+/233901 Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 21:30:25 +03:00
if c.IsLongTest() {
// Set a private hook in cmd/dist to run main Go repository tests
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// without the default -short flag. See go.dev/issue/12508.
dashboard: use a more consistent definition for longtest builders Previously, it was possible to define a builder whose IsLongTest method would report positively, such that it'd test golang.org/x repos in long test mode, but the main Go repository in short test mode. This would be the case for any builder with "-longtest" suffix if it did not manually include GO_TEST_SHORT=0 in its environment configuration. It's unlikely we would want to do that intentionally, so this refactor makes such misconfiguration less likely by inserting the GO_TEST_SHORT environment variable assignment into the output from Env automatically. Now, a longtest builder is defined in one consistent way: it must have a "-longtest" suffix, so that the IsLongTest method reports positively. For golang/go#39054. For golang/go#29252. For golang/go#12508. Change-Id: Ic24df7b3b7de7db728bba6dc6ad4dd38a2e61e82 Reviewed-on: https://go-review.googlesource.com/c/build/+/233901 Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 21:30:25 +03:00
env = append(env, "GO_TEST_SHORT=0")
}
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
env = append(env, c.HostConfig().env...)
dashboard: mark some builders as having flaky networks Follow-up to https://golang.org/cl/22852 Change-Id: I5f0cd25248a8892b7d1b0f14e87b12b8b9a8da3a Reviewed-on: https://go-review.googlesource.com/22883 Reviewed-by: Ian Lance Taylor <iant@golang.org>
2016-05-06 21:55:26 +03:00
return append(env, c.env...)
cmd/coordinator: set GO_BUILDER_NAME env var when exec'ing on buildlet This will allow tests to identify that they are running on the continuous build infrastructure and run extra and/or different tests. Fixes golang/go#11346 Change-Id: Iafe25babc764b7e012c05f0b62331b11690bf194 Reviewed-on: https://go-review.googlesource.com/13120 Reviewed-by: Russ Cox <rsc@golang.org>
2015-08-04 05:19:02 +03:00
}
all: add env support, freebsd-386, freebsd-amd64-race, re-enable plan9 Update golang/go#9491 Update golang/go#8639 Change-Id: I1f43c751777f10a6d5870ca9bbb8c2a3430189bf Reviewed-on: https://go-review.googlesource.com/3170 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-22 02:15:48 +03:00
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// ModulesEnv returns the extra module-specific environment variables
// to append to this builder as a function of the repo being built
// ("go", "oauth2", "net", etc).
func (c *BuildConfig) ModulesEnv(repo string) (env []string) {
dashboard: set the correct module proxy for EC2 builders This change sets the default module proxy address for EC2 builders. EC2 builders should have the same proxy address set as reverse builders. Fixes golang/go#40914 Change-Id: I4de2ed178170f60fdbe4e2f9aa6f024bb43ee020 Reviewed-on: https://go-review.googlesource.com/c/build/+/249577 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-20 18:53:58 +03:00
// EC2 and reverse builders should set the public module proxy
// address instead of the internal proxy.
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
if (c.HostConfig().isEC2 || c.IsReverse()) && repo != "go" && !c.PrivateGoProxy() {
cmd/coordinator: use proxy.golang.org instead of private Athens Fixes golang/go#31770 Change-Id: Ia21b3c835b3692351d83e00b9a8cb73db2103192 Reviewed-on: https://go-review.googlesource.com/c/build/+/175057 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-02 23:32:40 +03:00
env = append(env, "GOPROXY=https://proxy.golang.org")
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
}
switch repo {
dashboard: set GOPROXY=off for the "go" repo to catch more network usage Updates golang/go#30612 Updates golang/go#30760 Change-Id: I296f4f7a163c1bdd59e839229c0961b21f26da89 Reviewed-on: https://go-review.googlesource.com/c/build/+/167039 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 07:44:17 +03:00
case "go":
if !c.OutboundNetworkAllowed() {
env = append(env, "GOPROXY=off")
}
dashboard: set GO111MODULE=on for x/perf CL 191378 removed some +build appengine tags from ./analysis/appengine, so those packages now require GO111MODULE=on in order to resolve the dependency on google.golang.org/appengine. Fixes golang/go#33952 Change-Id: I20c9ba3f42d488265726fda9b1c790e48a1433b3 Reviewed-on: https://go-review.googlesource.com/c/build/+/192333 Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-08-29 21:26:25 +03:00
case "oauth2", "build", "perf", "website":
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
env = append(env, "GO111MODULE=on")
}
dashboard, cmd/coordinator: add controls to skip subrepo dirs in GOPATH mode This change adds controls to the dashboard package that makes it possible to skip certain directories in subrepos from being tested in GOPATH mode. It uses this control mechanism to skip the gopls directory in x/tools from being tested in GOPATH mode. That directory and everything inside is developed with support for module mode only. All other packages in x/tools continue to be supported both in module and GOPATH modes for the current and previous releases, as per release policy¹. ¹ https://golang.org/doc/devel/release.html#policy Fixes golang/go#34190 Change-Id: Icdb4d0e1419f69c84c9a3f9a33727a09a35599f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/194397 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-09-09 23:48:08 +03:00
return env
}
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
func (c *BuildConfig) IsReverse() bool { return c.HostConfig().IsReverse }
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
func (c *BuildConfig) IsContainer() bool { return c.HostConfig().IsContainer() }
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
func (c *HostConfig) IsContainer() bool { return c.ContainerImage != "" }
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
func (c *BuildConfig) IsVM() bool { return c.HostConfig().IsVM() }
dashboard: add host-linux-arm64-aws builder Add the host-linux-arm64-aws builder. The HostConfig IsVM method has been modified to support the concept that an EC2 VM can be created which runs the buildlet binary in a container. This configuration would have both a VM image and a container image set in the host configuration. For golang/go#36841 Change-Id: I092b48b1dda24d24bcd0b10dff0b2126f5f43017 Reviewed-on: https://go-review.googlesource.com/c/build/+/249118 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-18 20:32:05 +03:00
// IsVM reports whether the instance running the job is ultimately a VM. Hosts where
// a VM is used only to initiate a container are considered a container, not a VM.
// EC2 instances may be configured to run in containers that are running
// on custom AMIs.
func (c *HostConfig) IsVM() bool {
if c.isEC2 {
return c.VMImage != "" && c.ContainerImage == ""
}
return c.VMImage != ""
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
dashboard: create buildlet client package, move coordinator code into it Operation Packification, step 2 of tons. Eventually the buildlet client binary will use this stuff now. Change-Id: I4cf5f3e6beb9e56bdc795ed513ce6daaf61425e3 Reviewed-on: https://go-review.googlesource.com/2921 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-01-16 03:29:16 +03:00
func (c *BuildConfig) GOOS() string { return c.Name[:strings.Index(c.Name, "-")] }
func (c *BuildConfig) GOARCH() string {
arch := c.Name[strings.Index(c.Name, "-")+1:]
i := strings.Index(arch, "-")
if i == -1 {
return arch
}
return arch[:i]
}
cmd/coordinator: add SlowBots support, opt-in to different slow trybots This parses TRY= comments to opt-in to slower/difference trybots. This needs some docs/UI work yet. Updates golang/go#34501 Change-Id: I13a835520d7ac341bc86139b0a2118235bc83e60 Reviewed-on: https://go-review.googlesource.com/c/build/+/201338 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-16 09:02:29 +03:00
// MatchesSlowBotTerm reports whether some provided term from a
// TRY=... comment on a Run-TryBot+1 vote on Gerrit should match this
// build config.
func (c *BuildConfig) MatchesSlowBotTerm(term string) bool {
return term != "" && (term == c.Name || slowBotAliases[term] == c.Name)
}
cmd/coordinator: test sharding, better status, logs Also gomote updates which came about during the process of developing and debugging this. Change-Id: Ia53d674118a6b99bcdda7062d3b7161279b6ad52 Reviewed-on: https://go-review.googlesource.com/10463 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-28 07:51:25 +03:00
// FilePathJoin is mostly like filepath.Join (without the cleaning) except
// it uses the path separator of c.GOOS instead of the host system's.
func (c *BuildConfig) FilePathJoin(x ...string) string {
if c.GOOS() == "windows" {
return strings.Join(x, "\\")
}
return strings.Join(x, "/")
}
dashboard: add privileged flag for builders This change adds a privileged flag for builders. Updates golang/go#47521 Change-Id: Icbc72bc21dd4345da65c2e231f0f59af5dd05ca1 Reviewed-on: https://go-review.googlesource.com/c/build/+/370661 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2021-12-09 22:12:12 +03:00
func (c *BuildConfig) IsRestricted() bool {
return c.isRestricted
}
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
// DistTestsExecTimeout returns how long the coordinator should wait
// for a cmd/dist test execution to run the provided dist test names.
func (c *BuildConfig) DistTestsExecTimeout(distTests []string) time.Duration {
// TODO: consider using distTests? We never did before, but
// now we have the TestStats in the coordinator. Pass in a
// *buildstats.TestStats and use historical data times some
// fudge factor? For now just use the old 20 minute limit
// we've used since 2014, but scale it by the
// GO_TEST_TIMEOUT_SCALE for the super slow builders which
// struggle with, say, the cgo tests. (which should be broken
// up into separate dist tests or shards, like the test/ dir
// was)
d := 20 * time.Minute
cmd/coordinator: scale go test timeout by GO_TEST_TIMEOUT_SCALE Previously, this environment variable was used to scale test timeout only in the main repository. Use it when running go test on packages in other repositories too. This unfortunately means that if some tests get so slow that they timeout with the default go test timeout value, builders that use timeout scale will not report such findings. Hopefully most builders are as fast as viable, and timeout scaling is only used when there's no other viable alternative. Fixes golang/go#56968. Change-Id: I84d5ab504c1bd808815ec5962f713d71dfec6758 Reviewed-on: https://go-review.googlesource.com/c/build/+/453975 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
2022-11-29 02:50:15 +03:00
d *= time.Duration(c.GoTestTimeoutScale())
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
return d
}
cmd/coordinator: scale go test timeout by GO_TEST_TIMEOUT_SCALE Previously, this environment variable was used to scale test timeout only in the main repository. Use it when running go test on packages in other repositories too. This unfortunately means that if some tests get so slow that they timeout with the default go test timeout value, builders that use timeout scale will not report such findings. Hopefully most builders are as fast as viable, and timeout scaling is only used when there's no other viable alternative. Fixes golang/go#56968. Change-Id: I84d5ab504c1bd808815ec5962f713d71dfec6758 Reviewed-on: https://go-review.googlesource.com/c/build/+/453975 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
2022-11-29 02:50:15 +03:00
// GoTestTimeoutScale returns this builder's GO_TEST_TIMEOUT_SCALE value, or 1.
func (c *BuildConfig) GoTestTimeoutScale() int {
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
const pfx = "GO_TEST_TIMEOUT_SCALE="
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
for _, env := range [][]string{c.env, c.HostConfig().env} {
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
for _, kv := range env {
if strings.HasPrefix(kv, pfx) {
if n, err := strconv.Atoi(kv[len(pfx):]); err == nil && n > 0 {
return n
}
}
}
}
return 1
}
cmd/coordinator: finish the scheduler code, at least mostly Optimizations and tuning remain, but this should be tons better than what we had before (random). Updates golang/go#19178 Change-Id: Idb483a4c4209a012814322cc8b37b966ee4681de Reviewed-on: https://go-review.googlesource.com/c/build/+/205078 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-30 06:59:13 +03:00
// HostConfig returns the host configuration of c.
func (c *BuildConfig) HostConfig() *HostConfig {
cmd/coordinator, dashboard: scale test exec timeouts by GO_TEST_TIMEOUT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-14 05:18:06 +03:00
if c.testHostConf != nil {
return c.testHostConf
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
if c, ok := Hosts[c.HostType]; ok {
return c
}
panic(fmt.Sprintf("missing buildlet config for buildlet %q", c.Name))
}
dashboard: fix docs of BuildsRepoPostSubmit, GoBootstrapURL There were some copy-paste mistakes affecting the documentation of these two identifiers. This change corrects that. Change-Id: Ic619f19c4a659a9357c816ff7fb6b0cd7b3bccd1 Reviewed-on: https://go-review.googlesource.com/c/build/+/169437 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-03-26 20:45:16 +03:00
// GoBootstrapURL returns the URL of a built Go 1.4+ tar.gz for the
// build configuration type c, or empty string if there isn't one.
dashboard: rename Go14URL to goBootstrapURLTmpl and provide accessor Also update all users, and rename another template field. Includes changes to coordinator, gomote, and release. Change-Id: I1c4408eadbcb83d61063a910dfa18cc395952bc2 Reviewed-on: https://go-review.googlesource.com/20976 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-03-22 01:05:52 +03:00
func (c *BuildConfig) GoBootstrapURL(e *buildenv.Environment) string {
dashboard: update builders to Go 1.17.13 for bootstrap Compute GoBootstrapURL for all hosts. This removes another obviously computable field, assuming the bootstrap toolchains have all been uploaded with consistent names (as genbootstrap -upload now does). It also makes all builders work the same: they all start by downloading the bootstrap toolchain, instead of having some download and others use a toolchain installed into the boot image. The builders with pre-installed toolchains will continue to have those toolchains, but now nothing will use them, because the coordinator or gomote will see the GoBootstrapURL result and push an updated toolchain to $workdir/go1.4. As part of all this simplification, switch to Go 1.17.13 as the bootstrap toolchain, for golang/go#44505. (And also because we have no Go 1.4 for some of these platforms.) Updating the bootstrap toolchain again in a couple years will now be easy: run genbootstrap -upload '*' and then change GoBootstrap here. For golang/go#44505. (Won't be fixed until coordinator is redeployed.) Succeeded running all.bash/bat/rc using updated debugnewvm: android-386-emu android-amd64-emu dragonfly-amd64-622 freebsd-386-12_3 freebsd-386-13_0 freebsd-amd64-13_0 freebsd-amd64-race js-wasm linux-386 linux-386-buster linux-386-clang linux-386-longtest linux-386-sid linux-386-softfloat linux-386-stretch linux-amd64 linux-amd64-alpine linux-amd64-boringcrypto linux-amd64-bullseye linux-amd64-buster linux-amd64-clang linux-amd64-fedora linux-amd64-goamd64v3 linux-amd64-longtest linux-amd64-nocgo linux-amd64-noopt linux-amd64-nounified linux-amd64-perf linux-amd64-race linux-amd64-racecompile linux-amd64-sid linux-amd64-ssacheck linux-amd64-staticlockranking linux-amd64-stretch linux-amd64-unified linux-amd64-vmx netbsd-386-9_0 netbsd-amd64-9_0 openbsd-386-68 openbsd-386-70 openbsd-amd64-68 openbsd-amd64-70 windows-386-2008 windows-386-2012 windows-amd64-2008 windows-amd64-2012 windows-amd64-2016 windows-amd64-longtest windows-amd64-newcc-race windows-amd64-race Succeeded running make.bash using updated debugnewvm: linux-s390x-crosscompile Succeeded running make.bash using updated gomote (real time for put14 shown): aix-ppc64 (5.2s) darwin-amd64-10_14 (3.4s) darwin-amd64-10_15 (3.5s) darwin-amd64-11_0 (4.5s) darwin-amd64-12_0 (4.5s) darwin-amd64-nocgo (4.4s) darwin-amd64-race (4.2s) darwin-arm64-11 (1.7s) darwin-arm64-12 (1.8s) freebsd-arm64-dmgk (4.0s) freebsd-arm-paulzhol (35.1s) illumos-amd64 (5.9s) linux-amd64-wsl (126.7s) linux-arm64-aws (2.8s) linux-arm-aws (3.8s) linux-mips64le-rtrk (20.4s) linux-mips64-rtrk (16.0s) linux-mipsle-rtrk (16.3s) linux-mips-rtrk (16.3s) linux-ppc64-buildlet (4.7s) linux-ppc64le-buildlet (3.6s) linux-ppc64le-power9osu (5.6s) linux-riscv64-unmatched (38.2s) linux-s390x-ibm (4.4s) netbsd-arm64-bsiegert (35.0s) openbsd-arm64-jsing (64.9s) openbsd-mips64-jsing (154.2s) plan9-386-0intro (8.7s) plan9-arm (18.2s) windows-arm64-10 (7.1s) windows-arm64-11 (4.1s) Put14 failed using gomote: android-arm64-corellium (403 Forbidden in fetch) android-arm-corellium (403 Forbidden in fetch) ios-arm64-corellium (403 Forbidden in fetch) - fails build, kept old GOROOT_BOOTSTRAP linux-loong64-3a5000 (proxyconnect tcp: dial tcp 117.50.175.110:7890: i/o timeout) - falls back to preinstalled Go 1.18, kept old GOROOT_BOOTSTRAP Builds fine, failing tests but not on dashboard anyway: freebsd-386-11_4 freebsd-amd64-11_4 linux-amd64-androidemu plan9-386 Failed in same way as current builders: openbsd-386-70-n2d windows-386-2008-newcc windows-386-2012-newcc windows-amd64-2008-newcc windows-amd64-2012-newcc windows-amd64-2016-newcc windows-amd64-longtest-newcc Can't connect with gomote, so untested: linux-riscv64-jsing (but linux-riscv64-unmatched works) netbsd-arm-bsiegert openbsd-arm-jsing plan9-amd64-0intro solaris-amd64-oraclerel (but illumos-amd64 works) Change-Id: If4354a8681dbac28e1d34897b6356b881592c241 Reviewed-on: https://go-review.googlesource.com/c/build/+/419993 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-29 03:55:40 +03:00
hc := c.HostConfig()
if hc.GoBootstrap == "none" {
return ""
}
return "https://storage.googleapis.com/" + e.BuildletBucket +
"/gobootstrap-" + hc.HostArch + "-" + hc.GoBootstrap + ".tar.gz"
dashboard: rename Go14URL to goBootstrapURLTmpl and provide accessor Also update all users, and rename another template field. Includes changes to coordinator, gomote, and release. Change-Id: I1c4408eadbcb83d61063a910dfa18cc395952bc2 Reviewed-on: https://go-review.googlesource.com/20976 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-03-22 01:05:52 +03:00
}
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
// BuildletBinaryURL returns the public URL of this builder's buildlet.
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
func (c *HostConfig) BuildletBinaryURL(e *buildenv.Environment) string {
dashboard: compute BuildletURL instead of listing in table This removes an obviously computable field. (At least, now that the host names provide the GOOS-GOARCH.) One effect of this CL is that all VMs will have the buildlet URL available in metadata, even VMs that don't want it. Another effect is that all builders will use https, not unsecured http. (We even had some builders hosted outside Google Cloud that were downloading the buildlet over plain http.) It does not appear that any of the VMs are unable to speak https: I've run every VM using debugnewvm and all of them were able to start the buildlet (or else were not downloading it in the first place). Change-Id: I6f766c491a4848c5dc0e3d7537c7aeab7760a7f6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419986 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-07-26 19:29:51 +03:00
return "https://storage.googleapis.com/" + e.BuildletBucket + "/buildlet." + c.HostArch
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
}
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
// IsRace reports whether this is a race builder.
// A race builder runs tests without the -short flag.
//
// A builder is considered to be a race builder
// if and only if it one of the components of the builder
// name is "race" (components are delimited by "-").
cmd/coordinator: shard linux race builder Fixes golang/go#11074 Change-Id: I9401122e4d7febd3e38a80be89fcb2e03969f383 Reviewed-on: https://go-review.googlesource.com/11168 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-17 18:22:14 +03:00
func (c *BuildConfig) IsRace() bool {
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
for _, s := range strings.Split(c.Name, "-") {
if s == "race" {
return true
}
}
return false
cmd/coordinator: shard linux race builder Fixes golang/go#11074 Change-Id: I9401122e4d7febd3e38a80be89fcb2e03969f383 Reviewed-on: https://go-review.googlesource.com/11168 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-17 18:22:14 +03:00
}
dashboard: use a more consistent definition for longtest builders Previously, it was possible to define a builder whose IsLongTest method would report positively, such that it'd test golang.org/x repos in long test mode, but the main Go repository in short test mode. This would be the case for any builder with "-longtest" suffix if it did not manually include GO_TEST_SHORT=0 in its environment configuration. It's unlikely we would want to do that intentionally, so this refactor makes such misconfiguration less likely by inserting the GO_TEST_SHORT environment variable assignment into the output from Env automatically. Now, a longtest builder is defined in one consistent way: it must have a "-longtest" suffix, so that the IsLongTest method reports positively. For golang/go#39054. For golang/go#29252. For golang/go#12508. Change-Id: Ic24df7b3b7de7db728bba6dc6ad4dd38a2e61e82 Reviewed-on: https://go-review.googlesource.com/c/build/+/233901 Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 21:30:25 +03:00
// IsLongTest reports whether this is a longtest builder.
// A longtest builder runs tests without the -short flag.
//
// A builder is considered to be a longtest builder
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
// if and only if it one of the components of the builder
// name is "longtest" (components are delimited by "-").
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
func (c *BuildConfig) IsLongTest() bool {
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
for _, s := range strings.Split(c.Name, "-") {
if s == "longtest" {
return true
}
}
return false
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
}
dashboard: set GOPROXY=off for the "go" repo to catch more network usage Updates golang/go#30612 Updates golang/go#30760 Change-Id: I296f4f7a163c1bdd59e839229c0961b21f26da89 Reviewed-on: https://go-review.googlesource.com/c/build/+/167039 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 07:44:17 +03:00
// OutboundNetworkAllowed reports whether this builder should be
// allowed to make outbound network requests. This is only enforced
// on some builders. (Currently most Linux ones)
func (c *BuildConfig) OutboundNetworkAllowed() bool {
dashboard: remove vetall, update misc-compile builders Updates golang/go#31916 Change-Id: I38c08955bdb4ff2b0963d5c91c6e8f78267b8004 Reviewed-on: https://go-review.googlesource.com/c/build/+/176599 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-10 22:28:40 +03:00
return c.IsLongTest()
dashboard: set GOPROXY=off for the "go" repo to catch more network usage Updates golang/go#30612 Updates golang/go#30760 Change-Id: I296f4f7a163c1bdd59e839229c0961b21f26da89 Reviewed-on: https://go-review.googlesource.com/c/build/+/167039 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 07:44:17 +03:00
}
dashboard, cmd/coordinator: add -racecompile builder Change-Id: Idc5756f82081de6b5dfd17036f2bfc9cf11c5659 Reviewed-on: https://go-review.googlesource.com/41414 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-22 02:41:12 +03:00
func (c *BuildConfig) GoInstallRacePackages() []string {
if c.InstallRacePackages != nil {
return append([]string(nil), c.InstallRacePackages...)
}
if c.IsRace() {
return []string{"std"}
}
return nil
}
dashboard: move buildlet exec code from coordinator to client package Change-Id: I778ac78ed02be9f67436ec045a3816dfc24afda3 Reviewed-on: https://go-review.googlesource.com/2923 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-01-16 20:54:03 +03:00
// AllScript returns the relative path to the operating system's script to
// do the build and run its standard set of tests.
// Example values are "src/all.bash", "src/all.bat", "src/all.rc".
func (c *BuildConfig) AllScript() string {
dashboard: add sanity check Because almost all the BuildConfig methods indirectly call AllScript, add in a little defense against accident creation of BuildConfig zero values (of the value type, not nil pointers). This can happen by doing a lookup in a map[string]dashboard.BuildConfig and then calling a method on it. We should probably move everything to pointer values of BuildConfig. There aren't many value types remaining. This paranoia isn't a result of any bug yet, but rather than the result of discussion on CL 40477. Change-Id: Ic273d4de28ac8930b56bc232bf77a9ba39f99fad Reviewed-on: https://go-review.googlesource.com/40497 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-13 00:37:13 +03:00
if c.Name == "" {
panic("bogus BuildConfig")
}
cmd/coordinator: shard linux race builder Fixes golang/go#11074 Change-Id: I9401122e4d7febd3e38a80be89fcb2e03969f383 Reviewed-on: https://go-review.googlesource.com/11168 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-17 18:22:14 +03:00
if c.IsRace() {
all: add env support, freebsd-386, freebsd-amd64-race, re-enable plan9 Update golang/go#9491 Update golang/go#8639 Change-Id: I1f43c751777f10a6d5870ca9bbb8c2a3430189bf Reviewed-on: https://go-review.googlesource.com/3170 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-22 02:15:48 +03:00
if strings.HasPrefix(c.Name, "windows-") {
return "src/race.bat"
}
return "src/race.bash"
}
dashboard: move buildlet exec code from coordinator to client package Change-Id: I778ac78ed02be9f67436ec045a3816dfc24afda3 Reviewed-on: https://go-review.googlesource.com/2923 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-01-16 20:54:03 +03:00
if strings.HasPrefix(c.Name, "windows-") {
return "src/all.bat"
}
if strings.HasPrefix(c.Name, "plan9-") {
return "src/all.rc"
}
cmd/coordinator: shard the misc-compile builder over 4 builders Now that it's on Kubernetes, it's fast and cheap to shard it wider. Change-Id: I2858f4c417ef26661575a348fbfc47f4c25d81a2 Reviewed-on: https://go-review.googlesource.com/22795 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-05-05 03:42:49 +03:00
if strings.HasPrefix(c.Name, "misc-compile") {
dashboard: add all-compile builder Runs buildall.bash only. Change-Id: I1a68d54569ccb511d956c5b181e463503353d4d4 Reviewed-on: https://go-review.googlesource.com/9512 Reviewed-by: David Crawshaw <crawshaw@golang.org>
2015-04-30 00:44:46 +03:00
return "src/buildall.bash"
}
dashboard: move buildlet exec code from coordinator to client package Change-Id: I778ac78ed02be9f67436ec045a3816dfc24afda3 Reviewed-on: https://go-review.googlesource.com/2923 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-01-16 20:54:03 +03:00
return "src/all.bash"
}
dashboard, cmd/coordinator: only split make & run for builders where it'll work Change-Id: I1fdc27ea4adcc83fbd736d2bd1a34a07ca36a50c Reviewed-on: https://go-review.googlesource.com/10423 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-27 21:51:27 +03:00
// SplitMakeRun reports whether the coordinator should first compile
// (using c.MakeScript), then snapshot, then run the tests (ideally
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// sharded) using cmd/dist test.
dashboard, cmd/coordinator: only split make & run for builders where it'll work Change-Id: I1fdc27ea4adcc83fbd736d2bd1a34a07ca36a50c Reviewed-on: https://go-review.googlesource.com/10423 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-27 21:51:27 +03:00
// Eventually this function should always return true (and then be deleted)
// but for now we've only set up the scripts and verified that the main
// configurations work.
func (c *BuildConfig) SplitMakeRun() bool {
switch c.AllScript() {
build: move Linux and nacl builders to Kubernetes, add ssacheck trybot And shard the nacl builders. Fixes golang/go#15242 Fixes golang/go#12546 Change-Id: I3311678dbb64a76026f75f5691cffac0f25d976b Reviewed-on: https://go-review.googlesource.com/22780 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Ross Light <light@google.com>
2016-05-04 20:47:12 +03:00
case "src/all.bash", "src/all.bat",
"src/race.bash", "src/race.bat",
dashboard, env/linux-x86-nacl: remove nacl builders and supporting files Go 1.13 was the last release with nacl, and it's not supported by now. For golang/go#30439. Change-Id: Ic690aa388ab4505d5e755bbe40fed850a7300c69 Reviewed-on: https://go-review.googlesource.com/c/build/+/260200 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-10-07 18:12:00 +03:00
"src/all.rc":
dashboard, cmd/coordinator: only split make & run for builders where it'll work Change-Id: I1fdc27ea4adcc83fbd736d2bd1a34a07ca36a50c Reviewed-on: https://go-review.googlesource.com/10423 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-27 21:51:27 +03:00
// These we've verified to work.
return true
}
dashboard: remove iostest special case There are no tethered iOS builders left. If we add some in the future, they should use all.bash directly. Change-Id: Ieef7454af706c7e99c0d10fc37a337fb2c3ba130 Reviewed-on: https://go-review.googlesource.com/c/build/+/259357 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Elias Naur <mail@eliasnaur.com>
2020-10-03 12:22:43 +03:00
// TODO(bradfitz): buildall.bash should really just be N small container
// jobs instead of a "buildall.bash". Then we can delete this whole method.
dashboard, cmd/coordinator: only split make & run for builders where it'll work Change-Id: I1fdc27ea4adcc83fbd736d2bd1a34a07ca36a50c Reviewed-on: https://go-review.googlesource.com/10423 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-05-27 21:51:27 +03:00
return false
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
func (c *BuildConfig) IsTryOnly() bool { return c.tryOnly }
func (c *BuildConfig) NeedsGoProxy() bool { return c.needsGoProxy }
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
// PrivateGoProxy for builder has it's own Go proxy instead of proxy.golang.org
func (c *BuildConfig) PrivateGoProxy() bool { return c.privateGoProxy }
dashboard: fix docs of BuildsRepoPostSubmit, GoBootstrapURL There were some copy-paste mistakes affecting the documentation of these two identifiers. This change corrects that. Change-Id: Ic619f19c4a659a9357c816ff7fb6b0cd7b3bccd1 Reviewed-on: https://go-review.googlesource.com/c/build/+/169437 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-03-26 20:45:16 +03:00
// BuildsRepoPostSubmit reports whether the build configuration type c
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// should build the given repo ("go", "net", etc) and branch
// ("master", "release-branch.go1.12") as a post-submit build
// that shows up on https://build.golang.org/.
func (c *BuildConfig) BuildsRepoPostSubmit(repo, branch, goBranch string) bool {
if c.tryOnly {
dashboard: build sub-repos on more builders Change-Id: I57c12f427448281d71b8507ed950038209134143 Reviewed-on: https://go-review.googlesource.com/10915 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-06-11 20:01:24 +03:00
return false
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
return c.buildsRepoAtAll(repo, branch, goBranch)
cmd/coordinator: build sub-repositories Fixes golang/go#9506 Change-Id: Iebfb52386b5ba3df7d058f266e227d634d210ec6 Reviewed-on: https://go-review.googlesource.com/10732 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-06-05 02:45:17 +03:00
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// BuildsRepoTryBot reports whether the build configuration type c
// should build the given repo ("go", "net", etc) and branch
// ("master", "release-branch.go1.12") as a trybot.
func (c *BuildConfig) BuildsRepoTryBot(repo, branch, goBranch string) bool {
return c.tryBot != nil && c.tryBot(repo, branch, goBranch) && c.buildsRepoAtAll(repo, branch, goBranch)
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
}
cmd/coordinator: add a JSON mode to the /builders handler And add a test that indirectly verifies that the BuildConfig and HostConfig are JSON serializable. They weren't due to an exported func. But that exported func shouldn't be exported, so unexport it and move more policy into dashboard/builders.go. (There's been a number of recent cleanup CLs to move all policy into dashboard/builders.go instead of sprinkled all over the coordinator) A future CL will use this JSON in gomote create. Updates golang/go#30929 Change-Id: I726eaf6a4f3eeaab27d31e2642cb7642111ccd67 Reviewed-on: https://go-review.googlesource.com/c/build/+/168341 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-19 20:17:23 +03:00
// ShouldRunDistTest reports whether the named cmd/dist test should be
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
// run for this build config. The isNormalTry parameter is whether this
// is for a normal TryBot (non-SlowBot) run.
cmd/coordinator: add a JSON mode to the /builders handler And add a test that indirectly verifies that the BuildConfig and HostConfig are JSON serializable. They weren't due to an exported func. But that exported func shouldn't be exported, so unexport it and move more policy into dashboard/builders.go. (There's been a number of recent cleanup CLs to move all policy into dashboard/builders.go instead of sprinkled all over the coordinator) A future CL will use this JSON in gomote create. Updates golang/go#30929 Change-Id: I726eaf6a4f3eeaab27d31e2642cb7642111ccd67 Reviewed-on: https://go-review.googlesource.com/c/build/+/168341 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-19 20:17:23 +03:00
//
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
// In general, this returns true. When in normal trybot mode,
// some slow portable tests are only run on the fastest builder.
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
//
// Individual builders can adjust this policy to fit their needs.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func (c *BuildConfig) ShouldRunDistTest(distTest string, isNormalTry bool) bool {
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
run := true
// This section implements the default cmd/dist test policy.
// Any changes here will affect test coverage on all builders.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
if isNormalTry {
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
slowPortableTest := distTest == "api" // Whether a test is slow and has the same behavior everywhere.
fastestBuilder := c.Name == "linux-amd64"
if slowPortableTest && !fastestBuilder {
// Don't run the test on this builder.
run = false
}
cmd/coordinator: add a JSON mode to the /builders handler And add a test that indirectly verifies that the BuildConfig and HostConfig are JSON serializable. They weren't due to an exported func. But that exported func shouldn't be exported, so unexport it and move more policy into dashboard/builders.go. (There's been a number of recent cleanup CLs to move all policy into dashboard/builders.go instead of sprinkled all over the coordinator) A future CL will use this JSON in gomote create. Updates golang/go#30929 Change-Id: I726eaf6a4f3eeaab27d31e2642cb7642111ccd67 Reviewed-on: https://go-review.googlesource.com/c/build/+/168341 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-19 20:17:23 +03:00
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// Let individual builders adjust the cmd/dist test policy.
if c.distTestAdjust != nil {
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
run = c.distTestAdjust(run, distTest, isNormalTry)
cmd/coordinator: add a JSON mode to the /builders handler And add a test that indirectly verifies that the BuildConfig and HostConfig are JSON serializable. They weren't due to an exported func. But that exported func shouldn't be exported, so unexport it and move more policy into dashboard/builders.go. (There's been a number of recent cleanup CLs to move all policy into dashboard/builders.go instead of sprinkled all over the coordinator) A future CL will use this JSON in gomote create. Updates golang/go#30929 Change-Id: I726eaf6a4f3eeaab27d31e2642cb7642111ccd67 Reviewed-on: https://go-review.googlesource.com/c/build/+/168341 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-19 20:17:23 +03:00
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
cmd/coordinator: add a JSON mode to the /builders handler And add a test that indirectly verifies that the BuildConfig and HostConfig are JSON serializable. They weren't due to an exported func. But that exported func shouldn't be exported, so unexport it and move more policy into dashboard/builders.go. (There's been a number of recent cleanup CLs to move all policy into dashboard/builders.go instead of sprinkled all over the coordinator) A future CL will use this JSON in gomote create. Updates golang/go#30929 Change-Id: I726eaf6a4f3eeaab27d31e2642cb7642111ccd67 Reviewed-on: https://go-review.googlesource.com/c/build/+/168341 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-19 20:17:23 +03:00
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// buildsRepoAtAll reports whether we should do builds of the provided
// repo ("go", "sys", "net", etc). This applies to both post-submit
// and trybot builds. Use BuildsRepoPostSubmit for only post-submit
// or BuildsRepoTryBot for trybots.
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
//
// The branch is the branch of repo ("master",
// "release-branch.go1.12", etc); it is required. The goBranch is the
// branch of Go itself. It's required if repo != "go". When repo ==
// "go", the goBranch defaults to the value of branch.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
func (c *BuildConfig) buildsRepoAtAll(repo, branch, goBranch string) bool {
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
if goBranch == "" {
if repo == "go" {
goBranch = branch
} else {
panic("missing goBranch")
}
}
if branch == "" {
panic("missing branch")
}
if repo == "" {
panic("missing repo")
}
dashboard: skip Android build on older releases Also do some cleanup of no longer applicable policy. Fixes golang/go#30485 Change-Id: Id921ea5e7f60dda097be9ebba052a09349ea000a Reviewed-on: https://go-review.googlesource.com/c/164681 Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 02:20:41 +03:00
// Don't build old branches.
const minGo1x = 11
dashboard: require at least Go 1.12 for aix builder Fixes golang/go#30799 Change-Id: I0b3b53b715e2dc00f10548f74443224190003818 Reviewed-on: https://go-review.googlesource.com/c/build/+/167357 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 11:29:15 +03:00
for _, b := range []string{branch, goBranch} {
if bmaj, bmin, ok := version.ParseReleaseBranch(b); ok {
if bmaj != 1 || bmin < minGo1x {
return false
}
dashboard: fix vet warning Fix warning reported by "go vet": ./builders.go:1126:11: golang.org/x/build/types.MajorMinor struct literal uses unkeyed fields ./builders.go:1506:8: golang.org/x/build/types.MajorMinor struct literal uses unkeyed fields Change-Id: Ifa167bdcda4eb6123362353da58307dfb94174df Reviewed-on: https://go-review.googlesource.com/c/build/+/423034 Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-08-11 21:12:53 +03:00
bmm := types.MajorMinor{Major: bmaj, Minor: bmin}
dashboard: require at least Go 1.12 for aix builder Fixes golang/go#30799 Change-Id: I0b3b53b715e2dc00f10548f74443224190003818 Reviewed-on: https://go-review.googlesource.com/c/build/+/167357 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 11:29:15 +03:00
if bmm.Less(c.MinimumGoVersion) {
return false
}
dashboard: don't test the exp repo against release branches Exp is experimental. It's hard enough keeping it passing on master. We're not going to fight release branches as well. If somebody wants to see test coverage against three versions of Go, they can graduate their code out of experimental. Change-Id: I4695ce479c47bd56a4a58dba05d367d3de020c58 Reviewed-on: https://go-review.googlesource.com/c/build/+/170518 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-03 07:45:29 +03:00
if repo == "exp" {
// Don't test exp against release branches; it's experimental.
return false
}
dashboard: require at least Go 1.12 for aix builder Fixes golang/go#30799 Change-Id: I0b3b53b715e2dc00f10548f74443224190003818 Reviewed-on: https://go-review.googlesource.com/c/build/+/167357 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-13 11:29:15 +03:00
}
cmd/coordinator: move skip branch policy into dashboard This change takes care of a TODO comment. It makes the builder configuration more centralized and contained in the dashboard package. Invert it for consistency with BuildConfig.BuildRepo method. Updates golang/go#26791 Change-Id: I46368adadb85f2ec730da4fc0abe5fd6a112a7c7 Reviewed-on: https://go-review.googlesource.com/c/149738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-11-15 08:55:22 +03:00
}
dashboard: skip Android build on older releases Also do some cleanup of no longer applicable policy. Fixes golang/go#30485 Change-Id: Id921ea5e7f60dda097be9ebba052a09349ea000a Reviewed-on: https://go-review.googlesource.com/c/164681 Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 02:20:41 +03:00
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// Build dev.boringcrypto branches only on linux/amd64 and windows/386 (see go.dev/issue/26791).
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
if repo == "go" && (branch == "dev.boringcrypto" || strings.HasPrefix(branch, "dev.boringcrypto.")) {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
if c.Name != "linux-amd64" && !strings.HasPrefix(c.Name, "windows-386") {
cmd/coordinator: move skip branch policy into dashboard This change takes care of a TODO comment. It makes the builder configuration more centralized and contained in the dashboard package. Invert it for consistency with BuildConfig.BuildRepo method. Updates golang/go#26791 Change-Id: I46368adadb85f2ec730da4fc0abe5fd6a112a7c7 Reviewed-on: https://go-review.googlesource.com/c/149738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-11-15 08:55:22 +03:00
return false
}
}
dashboard: disable more builders Make exp off by default, as it barely passes anywhere. Lock in the places where it does pass. Also disable x/net master combined with Go 1.11 on FreeBSD 32-bit. It doesn't work on our builders and it'll never be fixed (we're not going to make changes to Go 1.11) and there's resistance to skipping those tests (my CL 170777), so I'm just turning off the builder. That's not ideal, but it's better than people getting used to red on the dashboard. Fixes golang/go#31221 Change-Id: Id0228e4b0ee73715a0c2da84f68dcfc989a48aaf Reviewed-on: https://go-review.googlesource.com/c/build/+/170782 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-05 08:26:05 +03:00
if repo != "go" && !c.SplitMakeRun() {
return false
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
if p := c.buildsRepo; p != nil {
return p(repo, branch, goBranch)
}
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
return buildRepoByDefault(repo)
dashboard: disable more builders Make exp off by default, as it barely passes anywhere. Lock in the places where it does pass. Also disable x/net master combined with Go 1.11 on FreeBSD 32-bit. It doesn't work on our builders and it'll never be fixed (we're not going to make changes to Go 1.11) and there's resistance to skipping those tests (my CL 170777), so I'm just turning off the builder. That's not ideal, but it's better than people getting used to red on the dashboard. Fixes golang/go#31221 Change-Id: Id0228e4b0ee73715a0c2da84f68dcfc989a48aaf Reviewed-on: https://go-review.googlesource.com/c/build/+/170782 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-05 08:26:05 +03:00
}
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// buildRepoByDefault reports whether builders should do builds
// for the given repo ("go", "net", etc.) by default.
//
// It's used directly by BuildConfig.buildsRepoAtAll method for
// builders with a nil BuildConfig.buildsRepo value.
// It's also used by many builders that provide a custom build
// repo policy (a non-nil BuildConfig.buildsRepo value) as part
// of making the decision of whether to build a given repo.
//
// As a result, it effectively implements the default build repo policy.
// Any changes here will affect repo coverage of many builders.
func buildRepoByDefault(repo string) bool {
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
switch repo {
case "go":
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// Build the main Go repository by default.
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
return true
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
case "mobile", "exp", "build", "vulndb":
// Don't build x/mobile, x/exp, x/build, x/vulndb by default.
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
//
// Builders need to explicitly opt-in to build these repos.
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
return false
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
default:
// Build all other golang.org/x repositories by default.
return true
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
}
cmd/coordinator: move skip branch policy into dashboard This change takes care of a TODO comment. It makes the builder configuration more centralized and contained in the dashboard package. Invert it for consistency with BuildConfig.BuildRepo method. Updates golang/go#26791 Change-Id: I46368adadb85f2ec730da4fc0abe5fd6a112a7c7 Reviewed-on: https://go-review.googlesource.com/c/149738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-11-15 08:55:22 +03:00
}
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
var (
dashboard: build vulndb only for 1.17 and later Don't build the vulndb repo for Go 1.16 (and earlier). It contains only code used by the Go team, so it need not work on older Go versions. Change-Id: Ic936e98f13ad897a138ece415fcda9e28084c21a Reviewed-on: https://go-review.googlesource.com/c/build/+/388934 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-03-02 01:13:09 +03:00
defaultPlusExp = defaultPlus("exp")
defaultPlusExpBuild = defaultPlus("exp", "build")
defaultPlusExpBuildVulnDB = defaultPlus("exp", "build", "vulndb")
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
)
dashboard: disable more builders Make exp off by default, as it barely passes anywhere. Lock in the places where it does pass. Also disable x/net master combined with Go 1.11 on FreeBSD 32-bit. It doesn't work on our builders and it'll never be fixed (we're not going to make changes to Go 1.11) and there's resistance to skipping those tests (my CL 170777), so I'm just turning off the builder. That's not ideal, but it's better than people getting used to red on the dashboard. Fixes golang/go#31221 Change-Id: Id0228e4b0ee73715a0c2da84f68dcfc989a48aaf Reviewed-on: https://go-review.googlesource.com/c/build/+/170782 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-05 08:26:05 +03:00
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
// defaultPlus returns a buildsRepo policy function that returns true for all
// all the repos listed, plus the default repos.
func defaultPlus(repos ...string) func(repo, branch, goBranch string) bool {
return func(repo, _, _ string) bool {
for _, r := range repos {
if r == repo {
return true
}
}
return buildRepoByDefault(repo)
dashboard: don't build x/build on so many builders It was kinda overkill. Change-Id: Ied7fc42aa59a1ed18cc1da20e51c8ed386d84629 Reviewed-on: https://go-review.googlesource.com/c/build/+/210378 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-12-07 08:14:28 +03:00
}
}
cmd/coordinator, dashboard: split build into 'make' and 'run' steps Change-Id: Ib60a601ef21163d5e0d1fed3a2609d9b719c616a Reviewed-on: https://go-review.googlesource.com/10073 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-05-21 07:02:38 +03:00
// AllScriptArgs returns the set of arguments that should be passed to the
dashboard: add darwin-arm/arm64 buildlets Tested by running a local coordinator on the darwin-arm64 builder. Change-Id: Id38faaa3275d6535b897f3c65df6d01ed9c1847e Reviewed-on: https://go-review.googlesource.com/9459 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-04-29 15:54:19 +03:00
// all.bash-equivalent script. Usually empty.
func (c *BuildConfig) AllScriptArgs() []string {
buildlet, cmd/coordinator: GCE quota accounting, fixes And deal with Preemptible resource exhaustion errors. And change all-compile to misc-compile and only do the builders not covered otherwise (Fixes #11073) And make the watcher serve git source. And cache and singleflight fetching of git source. And a million other things. Fixes golang/go#11073 Change-Id: I0f45610f0c6a06bd0c8ba9632b8624e00aeb52fc Reviewed-on: https://go-review.googlesource.com/10750 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-06-05 04:25:50 +03:00
return append([]string(nil), c.allScriptArgs...)
dashboard: add darwin-arm/arm64 buildlets Tested by running a local coordinator on the darwin-arm64 builder. Change-Id: Id38faaa3275d6535b897f3c65df6d01ed9c1847e Reviewed-on: https://go-review.googlesource.com/9459 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-04-29 15:54:19 +03:00
}
cmd/release: add new program to build releases The release command will replace misc/makerelease from the main repo. The contents of makerelease make their way into this program. Also add GorootFinal and MakeScript methods to dashboard.BuildConfig. Change-Id: Id20f3f7a85a21f040d8cf47e438d299d57360556 Reviewed-on: https://go-review.googlesource.com/3693 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-02-02 15:05:01 +03:00
// MakeScript returns the relative path to the operating system's script to
// do the build.
// Example values are "src/make.bash", "src/make.bat", "src/make.rc".
func (c *BuildConfig) MakeScript() string {
if strings.HasPrefix(c.Name, "windows-") {
return "src/make.bat"
}
if strings.HasPrefix(c.Name, "plan9-") {
return "src/make.rc"
}
return "src/make.bash"
}
cmd/coordinator, dashboard: split build into 'make' and 'run' steps Change-Id: Ib60a601ef21163d5e0d1fed3a2609d9b719c616a Reviewed-on: https://go-review.googlesource.com/10073 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-05-21 07:02:38 +03:00
// MakeScriptArgs returns the set of arguments that should be passed to the
// make.bash-equivalent script. Usually empty.
func (c *BuildConfig) MakeScriptArgs() []string {
return c.AllScriptArgs()
}
cmd/release: add new program to build releases The release command will replace misc/makerelease from the main repo. The contents of makerelease make their way into this program. Also add GorootFinal and MakeScript methods to dashboard.BuildConfig. Change-Id: Id20f3f7a85a21f040d8cf47e438d299d57360556 Reviewed-on: https://go-review.googlesource.com/3693 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-02-02 15:05:01 +03:00
// GorootFinal returns the default install location for
// releases for this platform.
func (c *BuildConfig) GorootFinal() string {
if strings.HasPrefix(c.Name, "windows-") {
return "c:\\go"
}
return "/usr/local/go"
}
dashboard: do not add -standard-8 or -standard-16 to AWS machine types Reported buildlet failure says err=unknown EC2 vm type: m6g.xlarge-standard-16. Oops. Change-Id: I510bbb4a5bbf83f39d95305011c2d294cf876be5 Reviewed-on: https://go-review.googlesource.com/c/build/+/420755 Run-TryBot: Russ Cox <rsc@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-02 20:31:54 +03:00
// MachineType returns the AWS or GCE machine type to use for this builder.
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
func (c *HostConfig) MachineType() string {
dashboard: do not add -standard-8 or -standard-16 to AWS machine types Reported buildlet failure says err=unknown EC2 vm type: m6g.xlarge-standard-16. Oops. Change-Id: I510bbb4a5bbf83f39d95305011c2d294cf876be5 Reviewed-on: https://go-review.googlesource.com/c/build/+/420755 Run-TryBot: Russ Cox <rsc@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-02 20:31:54 +03:00
if c.IsEC2() {
return c.machineType
}
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
typ := c.machineType
if typ == "" {
if c.NestedVirt || c.MinCPUPlatform != "" {
// e2 instances do not support nested virtualization, but n2 instances do.
// Same for MinCPUPlatform: https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform#limitations
typ = "n2"
} else {
typ = "e2"
}
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
}
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
if strings.Contains(typ, "-") { // full type like "n2-standard-8"
return typ
dashboard: use n2 instances where necessary e2 and n2d instances do not support specifying a MinCPUVersion or NestedVirt. For golang/go#48969 Change-Id: I0c4b359b29cd24302b869748014f848a9b7b5e39 Reviewed-on: https://go-review.googlesource.com/c/build/+/356071 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-10-15 04:54:32 +03:00
}
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
if c.IsContainer() {
// Set a higher default machine size for containers,
// so their /workdir tmpfs can be larger. The COS
// image has no swap, so we want to make sure the
// /workdir fits completely in memory.
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
return typ + "-standard-16" // 16 vCPUs, 64 GB mem
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
}
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
return typ + "-standard-8" // 8 vCPUs, 32 GB mem
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
}
dashboard, buildenv: label EC2 instances This change adds a boolean which identified when an instance is an EC2 instance. Various EC2 related variables have been renamed to be more consistent. Updates golang/go#36841 Change-Id: Ief385bf9d41e320ebd7d31bc0108e8053f337afd Reviewed-on: https://go-review.googlesource.com/c/build/+/233801 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 20:27:15 +03:00
// IsEC2 returns true if the machine type is an EC2 arm64 type.
func (c *HostConfig) IsEC2() bool {
return c.isEC2
}
cmd/coordinator: fix the /builders page, add Host info Change-Id: I8828d62918e29c732592d82f49c48a8c3442c7f3 Reviewed-on: https://go-review.googlesource.com/29674 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 03:06:28 +03:00
// PoolName returns a short summary of the builder's host type for the
all: upgrade farmer.golang.org links to https Since farmer.golang.org has a valid certificate in production now, we should use that certificate for retrieving data. Change-Id: I3685d84953ea11e6ac09b4692fa27c73538a565c Reviewed-on: https://go-review.googlesource.com/39290 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-03 17:51:28 +03:00
// https://farmer.golang.org/builders page.
cmd/coordinator: fix the /builders page, add Host info Change-Id: I8828d62918e29c732592d82f49c48a8c3442c7f3 Reviewed-on: https://go-review.googlesource.com/29674 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 03:06:28 +03:00
func (c *HostConfig) PoolName() string {
switch {
case c.IsReverse:
return "Reverse (dedicated machine/VM)"
dashboard, buildenv: label EC2 instances This change adds a boolean which identified when an instance is an EC2 instance. Various EC2 related variables have been renamed to be more consistent. Updates golang/go#36841 Change-Id: Ief385bf9d41e320ebd7d31bc0108e8053f337afd Reviewed-on: https://go-review.googlesource.com/c/build/+/233801 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 20:27:15 +03:00
case c.IsEC2():
env/linux-arm64/aws, dashboard: update linux-arm64 builder image This updates the instruction for creating a VM image and a buildlet container image. The instructions will provide a better description for the steps required to create the images. The VM image has been updated to no longer require sudo when the docker command is executed. The host configuration has been updated with a new VM type and VM image. The rundockerbuildlet service configuration has been modified: * The memory limit has been removed because rundockerbuildlet will now use all of the available memory for buildlets running on AWS. * The service will report as running even after rundockerbuildlet has exited. Rundockerbuildlet will initiate a single buildlet and then exit. * The service will not be restarted after rundockerbuildlet has exited. Changes made to rundockerbuildlet which required these changes have been made in CL 234114. Updates golang/go#36841 Change-Id: I3ff51e414b11a2b1427cbd7c6e24e9135fc2a5c3 Reviewed-on: https://go-review.googlesource.com/c/build/+/236297 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-20 00:26:14 +03:00
return "EC2 VM Container"
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
case c.IsVM():
cmd/coordinator: fix the /builders page, add Host info Change-Id: I8828d62918e29c732592d82f49c48a8c3442c7f3 Reviewed-on: https://go-review.googlesource.com/29674 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 03:06:28 +03:00
return "GCE VM"
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
case c.IsContainer():
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
return "Container"
cmd/coordinator: fix the /builders page, add Host info Change-Id: I8828d62918e29c732592d82f49c48a8c3442c7f3 Reviewed-on: https://go-review.googlesource.com/29674 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 03:06:28 +03:00
}
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
panic("unknown builder type")
}
env/linux-x86-vmx: add new Debian host that's like Container-Optimized OS + vmx This adds scripts to create a new builder host image that acts like Container-Optimized OS (has docker, runs konlet on startup) but with a Debian 9 kernel + userspace that permits KVM for nested virtualization. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ib1d3a250556703856083c222be2a70c4e8d91884 Reviewed-on: https://go-review.googlesource.com/c/163301 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-22 00:10:54 +03:00
// ContainerVMImage returns the base VM name (not the fully qualified
// URL resource name of the VM) that starts the konlet program that
dashboard, buildlet, cmd/debugnewvm: clean up HostConfig.ContainerVMImage The debugnewvm command was printing out the wrong VM name, since the old method had also assumed (but not documented) that it only applied to nested virtualization containers. But remove that requirement and make the empty string mean unspecified instead (which we currently mean to use Container-Optimized OS) role and then use its new definition. Change-Id: Ieca138285aa567b1c24d585c5aa180f8a1534154 Reviewed-on: https://go-review.googlesource.com/c/build/+/177919 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-05-17 23:08:13 +03:00
// pulls & runs a container.
// The empty string means that no particular VM image is required
// and the caller can run this container in any host.
//
// This method is only applicable when c.IsContainer() is true.
env/linux-x86-vmx: add new Debian host that's like Container-Optimized OS + vmx This adds scripts to create a new builder host image that acts like Container-Optimized OS (has docker, runs konlet on startup) but with a Debian 9 kernel + userspace that permits KVM for nested virtualization. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ib1d3a250556703856083c222be2a70c4e8d91884 Reviewed-on: https://go-review.googlesource.com/c/163301 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-22 00:10:54 +03:00
func (c *HostConfig) ContainerVMImage() string {
if c.KonletVMImage != "" {
return c.KonletVMImage
}
dashboard, buildlet, cmd/debugnewvm: clean up HostConfig.ContainerVMImage The debugnewvm command was printing out the wrong VM name, since the old method had also assumed (but not documented) that it only applied to nested virtualization containers. But remove that requirement and make the empty string mean unspecified instead (which we currently mean to use Container-Optimized OS) role and then use its new definition. Change-Id: Ieca138285aa567b1c24d585c5aa180f8a1534154 Reviewed-on: https://go-review.googlesource.com/c/build/+/177919 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-05-17 23:08:13 +03:00
if c.NestedVirt {
all: switch vmx-enabled Debian over to Bullseye I basically just did a find-and-replace, and we'll see if it works? I've updated and built the new disk images so this should be ready to deploy. For golang/go#56414. Change-Id: Iaac41d6f7a1244c3682e624f7a4ee4fa7477dfa1 Reviewed-on: https://go-review.googlesource.com/c/build/+/445617 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:01:19 +03:00
return "debian-bullseye-vmx"
dashboard, buildlet, cmd/debugnewvm: clean up HostConfig.ContainerVMImage The debugnewvm command was printing out the wrong VM name, since the old method had also assumed (but not documented) that it only applied to nested virtualization containers. But remove that requirement and make the empty string mean unspecified instead (which we currently mean to use Container-Optimized OS) role and then use its new definition. Change-Id: Ieca138285aa567b1c24d585c5aa180f8a1534154 Reviewed-on: https://go-review.googlesource.com/c/build/+/177919 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-05-17 23:08:13 +03:00
}
env/linux-arm64/aws, dashboard: update linux-arm64 builder image This updates the instruction for creating a VM image and a buildlet container image. The instructions will provide a better description for the steps required to create the images. The VM image has been updated to no longer require sudo when the docker command is executed. The host configuration has been updated with a new VM type and VM image. The rundockerbuildlet service configuration has been modified: * The memory limit has been removed because rundockerbuildlet will now use all of the available memory for buildlets running on AWS. * The service will report as running even after rundockerbuildlet has exited. Rundockerbuildlet will initiate a single buildlet and then exit. * The service will not be restarted after rundockerbuildlet has exited. Changes made to rundockerbuildlet which required these changes have been made in CL 234114. Updates golang/go#36841 Change-Id: I3ff51e414b11a2b1427cbd7c6e24e9135fc2a5c3 Reviewed-on: https://go-review.googlesource.com/c/build/+/236297 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-20 00:26:14 +03:00
if c.isEC2 && c.ContainerImage != "" {
return fmt.Sprintf("gcr.io/%s/%s", buildenv.Production.ProjectName, c.ContainerImage)
}
dashboard, buildlet, cmd/debugnewvm: clean up HostConfig.ContainerVMImage The debugnewvm command was printing out the wrong VM name, since the old method had also assumed (but not documented) that it only applied to nested virtualization containers. But remove that requirement and make the empty string mean unspecified instead (which we currently mean to use Container-Optimized OS) role and then use its new definition. Change-Id: Ieca138285aa567b1c24d585c5aa180f8a1534154 Reviewed-on: https://go-review.googlesource.com/c/build/+/177919 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-05-17 23:08:13 +03:00
return ""
env/linux-x86-vmx: add new Debian host that's like Container-Optimized OS + vmx This adds scripts to create a new builder host image that acts like Container-Optimized OS (has docker, runs konlet on startup) but with a Debian 9 kernel + userspace that permits KVM for nested virtualization. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ib1d3a250556703856083c222be2a70c4e8d91884 Reviewed-on: https://go-review.googlesource.com/c/163301 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-22 00:10:54 +03:00
}
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
// IsHermetic reports whether this host config gets a fresh
// environment (including /usr, /var, etc) for each execution. This is
// true for VMs, GKE, and reverse buildlets running their containers
// running in Docker, but false on some reverse buildlets.
func (c *HostConfig) IsHermetic() bool {
switch {
case c.IsReverse:
return c.HermeticReverse
dashboard, buildenv: label EC2 instances This change adds a boolean which identified when an instance is an EC2 instance. Various EC2 related variables have been renamed to be more consistent. Updates golang/go#36841 Change-Id: Ief385bf9d41e320ebd7d31bc0108e8053f337afd Reviewed-on: https://go-review.googlesource.com/c/build/+/233801 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-13 20:27:15 +03:00
case c.IsEC2():
return true
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
case c.IsVM():
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
return true
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
case c.IsContainer():
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
return true
}
panic("unknown builder type")
cmd/coordinator: fix the /builders page, add Host info Change-Id: I8828d62918e29c732592d82f49c48a8c3442c7f3 Reviewed-on: https://go-review.googlesource.com/29674 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-23 03:06:28 +03:00
}
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
// IsGoogle reports whether this host is operated by Google,
// implying that we trust it to be secure and available.
func (c *HostConfig) IsGoogle() bool {
if c.IsContainer() || c.IsVM() {
return true
}
if c.IsReverse && c.GoogleReverse {
return true
}
return false
}
dashboard: try to speed up pre-submit longtest builders The longtest builders are currently primarily post-submit builders, where it's okay for them to be as slow as they need to be in order to provide additional test coverage. In this context, whether they take 40 minutes or 50 makes little difference. The longtest builders are also sometimes requested via SlowBots for changes that are riskier than usual, or otherwise desire additional coverage beyond the normal TryBots. They're also always enabled for CLs to release branches. In such contexts, speeding up SlowBot runs from 40 minutes to 20 or less would be appreciated and in turn help people use longtest SlowBots more frequently. Longtest builders are already configured to use sharded tests. Configure them to use additional helpers to speed up test execution. Try out 3, 5, and 9 helpers to see how much it helps before settling. For golang/go#37439. Change-Id: I425bc0257b7a54bb32c0eb1719fea7ba3f4fd461 Reviewed-on: https://go-review.googlesource.com/c/build/+/268037 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-06 15:55:36 +03:00
// NumTestHelpers reports how many additional buildlets
// past the first one to help out with sharded tests.
//
// isTry specifies whether it's for a pre-submit test
// run (a TryBot or SlowBot) where speed matters more.
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
func (c *BuildConfig) NumTestHelpers(isTry bool) int {
if isTry && c.numTryTestHelpers != 0 {
return c.numTryTestHelpers
}
return c.numTestHelpers
}
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
// defaultTrySet returns a trybot policy function that reports whether
// a project should use trybots. All the default projects are included,
// plus any given in extraProj.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
func defaultTrySet(extraProj ...string) func(proj, branch, goBranch string) bool {
return func(proj, branch, goBranch string) bool {
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
if proj == "go" {
return true
}
for _, p := range extraProj {
if proj == p {
return true
}
}
switch proj {
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
case "grpc-review":
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
return false
}
return true
}
}
// explicitTrySet returns a trybot policy function that reports
// whether a project should use trybots. Only the provided projects in
// projs are enabled.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
func explicitTrySet(projs ...string) func(proj, branch, goBranch string) bool {
return func(proj, branch, goBranch string) bool {
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
for _, p := range projs {
if proj == p {
return true
}
}
return false
}
}
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
func init() {
dashboard,env/freebsd: add 12.3-STABLE With the XSAVE bug fix. For golang/go#49967, golang/go#46272. Change-Id: Ie0711ba83e4f15d26e6fe89e89c80b7c3ad2c23c Reviewed-on: https://go-review.googlesource.com/c/build/+/375695 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-05 20:21:24 +03:00
addBuilder(BuildConfig{
Name: "freebsd-amd64-12_3",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-freebsd-amd64-12_3",
dashboard,env/freebsd: add 12.3-STABLE With the XSAVE bug fix. For golang/go#49967, golang/go#46272. Change-Id: Ie0711ba83e4f15d26e6fe89e89c80b7c3ad2c23c Reviewed-on: https://go-review.googlesource.com/c/build/+/375695 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-05 20:21:24 +03:00
tryBot: defaultTrySet("sys"),
distTestAdjust: fasterTrybots, // If changing this policy, update TestShouldRunDistTest accordingly.
numTryTestHelpers: 4,
})
addBuilder(BuildConfig{
Name: "freebsd-386-12_3",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-freebsd-amd64-12_3",
dashboard,env/freebsd: add 12.3-STABLE With the XSAVE bug fix. For golang/go#49967, golang/go#46272. Change-Id: Ie0711ba83e4f15d26e6fe89e89c80b7c3ad2c23c Reviewed-on: https://go-review.googlesource.com/c/build/+/375695 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-05 20:21:24 +03:00
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
distTestAdjust: fasterTrybots,
numTryTestHelpers: 4,
})
all: add env support, freebsd-386, freebsd-amd64-race, re-enable plan9 Update golang/go#9491 Update golang/go#8639 Change-Id: I1f43c751777f10a6d5870ca9bbb8c2a3430189bf Reviewed-on: https://go-review.googlesource.com/3170 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-22 02:15:48 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "freebsd-amd64-race",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-freebsd-amd64-13_0",
dashboard: add FreeBSD 11 builders Fixes golang/go#19097 Change-Id: I29725ef511f03e10d93561889b1a4a00eb959177 Reviewed-on: https://go-review.googlesource.com/37498 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-02-27 19:05:25 +03:00
})
dashboard: add freebsd-[amd64|386]-13_0 builders This change adds builders for FreeBSD 13.0. Updates golang/go#46272 Fixes golang/go#45903 Change-Id: I92f68f8d5eeee2d3bae8864dbfe5ee61b93ea677 Reviewed-on: https://go-review.googlesource.com/c/build/+/365314 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-19 00:33:40 +03:00
addBuilder(BuildConfig{
Name: "freebsd-amd64-13_0",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-freebsd-amd64-13_0",
dashboard: add freebsd-[amd64|386]-13_0 builders This change adds builders for FreeBSD 13.0. Updates golang/go#46272 Fixes golang/go#45903 Change-Id: I92f68f8d5eeee2d3bae8864dbfe5ee61b93ea677 Reviewed-on: https://go-review.googlesource.com/c/build/+/365314 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-19 00:33:40 +03:00
tryBot: explicitTrySet("sys"),
distTestAdjust: fasterTrybots, // If changing this policy, update TestShouldRunDistTest accordingly.
numTryTestHelpers: 4,
})
addBuilder(BuildConfig{
Name: "freebsd-386-13_0",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-freebsd-amd64-13_0",
dashboard: add freebsd-[amd64|386]-13_0 builders This change adds builders for FreeBSD 13.0. Updates golang/go#46272 Fixes golang/go#45903 Change-Id: I92f68f8d5eeee2d3bae8864dbfe5ee61b93ea677 Reviewed-on: https://go-review.googlesource.com/c/build/+/365314 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-19 00:33:40 +03:00
tryBot: explicitTrySet("sys"),
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
distTestAdjust: fasterTrybots,
numTryTestHelpers: 4,
})
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "linux-386",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: fasterTrybots,
tryBot: defaultTrySet(),
dashboard: update Debian version for 386 builders This change updates various linux-386 builders after the release of bullseye: - linux-386 has been updated to bullseye. - linux-386-jessie has had the notes updated. - linux-386-buster has been added. Updates golang/go#47721 Change-Id: Iab0048fcad4d51839013074a51ad37b424d3a7af Reviewed-on: https://go-review.googlesource.com/c/build/+/343632 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-19 00:45:09 +03:00
Notes: "Debian stable (currently Debian bullseye).",
env, buildlet, dashboard: support outbound firewalls for Linux Updates golang/go#30612 Change-Id: Ib13a286d0944a7f4a13b9e93a01533693052858b Reviewed-on: https://go-review.googlesource.com/c/build/+/165637 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 05:06:17 +03:00
env: []string{
"GOARCH=386",
"GOHOSTARCH=386",
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
env, buildlet, dashboard: support outbound firewalls for Linux Updates golang/go#30612 Change-Id: Ib13a286d0944a7f4a13b9e93a01533693052858b Reviewed-on: https://go-review.googlesource.com/c/build/+/165637 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 05:06:17 +03:00
},
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
numTestHelpers: 1,
numTryTestHelpers: 3,
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
})
dashboard: add linux-386-softfloat builder It's based on the linux-386-387 builder, but with GO386=softfloat and Debian 9 (stretch) instead of Debian 8 (jessie). Test it on a subset of golang.org/x repos (golang.org/x/crypto), since that should provide sufficient test coverage. For golang/go#41840. For golang/go#41848. Change-Id: Ida95fce198056a05c359ac5ab816c582bdd5930f Reviewed-on: https://go-review.googlesource.com/c/build/+/260201 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-10-07 18:24:42 +03:00
addBuilder(BuildConfig{
Name: "linux-386-softfloat",
Notes: "GO386=softfloat",
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
return repo == "go" || repo == "crypto"
dashboard: add linux-386-softfloat builder It's based on the linux-386-387 builder, but with GO386=softfloat and Debian 9 (stretch) instead of Debian 8 (jessie). Test it on a subset of golang.org/x repos (golang.org/x/crypto), since that should provide sufficient test coverage. For golang/go#41840. For golang/go#41848. Change-Id: Ida95fce198056a05c359ac5ab816c582bdd5930f Reviewed-on: https://go-review.googlesource.com/c/build/+/260201 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-10-07 18:24:42 +03:00
},
dashboard/builders: upgrade non-specific Linux builders to Stretch We have to update the non-versioned builders sometime, and now seems as good as any. This is just an easy first step, still need to figure out vmx and whether to disable the stretch builders on master/1.20. For golang/go#56414. Change-Id: I7f1ce4faa9c6fa1595b7a0c3c72d451b1d18e5f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/445616 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-26 20:52:15 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: add linux-386-softfloat builder It's based on the linux-386-387 builder, but with GO386=softfloat and Debian 9 (stretch) instead of Debian 8 (jessie). Test it on a subset of golang.org/x repos (golang.org/x/crypto), since that should provide sufficient test coverage. For golang/go#41840. For golang/go#41848. Change-Id: Ida95fce198056a05c359ac5ab816c582bdd5930f Reviewed-on: https://go-review.googlesource.com/c/build/+/260201 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-10-07 18:24:42 +03:00
env: []string{"GOARCH=386", "GOHOSTARCH=386", "GO386=softfloat"},
})
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
addBuilder(BuildConfig{
dashboard/builders: don't run mobile on Stretch builders, clean up I forgot to check buildRepoByDefault on the Stretch builders, so they started running x/mobile. Also noticed a ton of obsolete builders/checks, clean them out while I'm at it. In the tests, clear out very old version checks, and replace "arbitrary release branch" versions with go1.99 rather than whatever happened to be current when the test case was written. For golang/go#56414. Change-Id: I88eeeaec5d166d1ac1a3938dbc26870ff8d4b33a Reviewed-on: https://go-review.googlesource.com/c/build/+/446183 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-28 21:17:45 +03:00
Name: "linux-amd64",
HostType: "host-linux-amd64-bullseye",
tryBot: defaultTrySet(),
buildsRepo: defaultPlusExpBuildVulnDB,
env, buildlet, dashboard: support outbound firewalls for Linux Updates golang/go#30612 Change-Id: Ib13a286d0944a7f4a13b9e93a01533693052858b Reviewed-on: https://go-review.googlesource.com/c/build/+/165637 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 05:06:17 +03:00
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
env, buildlet, dashboard: support outbound firewalls for Linux Updates golang/go#30612 Change-Id: Ib13a286d0944a7f4a13b9e93a01533693052858b Reviewed-on: https://go-review.googlesource.com/c/build/+/165637 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 05:06:17 +03:00
},
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
numTestHelpers: 1,
numTryTestHelpers: 4,
all: run dev coordinator locally, allow debug in prod * flag allows debug (trigger a build) in prod mode * use default zone (us-central1-f) in staging * compute.CloudPlatformScope satisfies compute and storage scope requirements * new buildlet for linux-amd64 on Kubernetes Updates golang/go#12546 Change-Id: I1a0cbc0e0c0552b7ac56943c646378194508d48f Reviewed-on: https://go-review.googlesource.com/17102 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-11-20 21:00:06 +03:00
})
dashboard: add linux-amd64-boringcrypto builder As of CL 397895, GOEXPERIMENT=boringcrypto is understood on the master branch (and is a no-op). This CL adds a linux-amd64-boringcrypto builder in advance of merging actual boringcrypto code behind that GOEXPERIMENT flag. For golang/go#51940. Change-Id: I6611caf8f7a10f334e5343cadaf3b1c1e5bf4b2f Reviewed-on: https://go-review.googlesource.com/c/build/+/395815 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-03-25 20:18:35 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-boringcrypto",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: add linux-amd64-boringcrypto builder As of CL 397895, GOEXPERIMENT=boringcrypto is understood on the master branch (and is a no-op). This CL adds a linux-amd64-boringcrypto builder in advance of merging actual boringcrypto code behind that GOEXPERIMENT flag. For golang/go#51940. Change-Id: I6611caf8f7a10f334e5343cadaf3b1c1e5bf4b2f Reviewed-on: https://go-review.googlesource.com/c/build/+/395815 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-03-25 20:18:35 +03:00
Notes: "GOEXPERIMENT=boringcrypto",
tryBot: defaultTrySet(),
env: []string{
"GOEXPERIMENT=boringcrypto",
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
numTestHelpers: 1,
numTryTestHelpers: 4,
dashboard: replace GoDeps with release branch filters relui doesn't evaluate GoDeps when deciding what builders apply to which release branches, and at this point they're all in the past release anyway. For golang/go#48523. Change-Id: I9d1e89ec7583bbc82712fe946a5e9122e67b66b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/435498 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:39:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return atLeastGo1(goBranch, 19) && buildRepoByDefault(repo)
dashboard: add linux-amd64-boringcrypto builder As of CL 397895, GOEXPERIMENT=boringcrypto is understood on the master branch (and is a no-op). This CL adds a linux-amd64-boringcrypto builder in advance of merging actual boringcrypto code behind that GOEXPERIMENT flag. For golang/go#51940. Change-Id: I6611caf8f7a10f334e5343cadaf3b1c1e5bf4b2f Reviewed-on: https://go-review.googlesource.com/c/build/+/395815 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-03-25 20:18:35 +03:00
},
})
dashboard, buildlet: add a disabled builder with nested virt, for testing This adds a linux-amd64 COS builder that should be just like our existing linux-amd64 COS builder except that it's using a forked image that has the VMX license bit enabled for nested virtualization. (GCE appears to be using the license mechanism as some sort of opt-in mechanism for features that aren't yet GA; might go away?) Once this is in, it won't do any new builds as regular+trybot builders are disabled. But it means I can then use gomote + debugnewvm to work on preparing the other four image types. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ic55f17eea17908dba7f58618d8cd162a2ed9b015 Reviewed-on: https://go-review.googlesource.com/c/162959 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-16 01:05:42 +03:00
addBuilder(BuildConfig{
all: add a macOS 10.14 (Mojave) builder Fixes golang/go#27806 Change-Id: I576f563acb2c50cd0456cd4e6a1271b9aa59c9df Reviewed-on: https://go-review.googlesource.com/c/build/+/169498 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-27 02:04:31 +03:00
Name: "linux-amd64-vmx",
all: switch vmx-enabled Debian over to Bullseye I basically just did a find-and-replace, and we'll see if it works? I've updated and built the new disk images so this should be ready to deploy. For golang/go#56414. Change-Id: Iaac41d6f7a1244c3682e624f7a4ee4fa7477dfa1 Reviewed-on: https://go-review.googlesource.com/c/build/+/445617 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:01:19 +03:00
HostType: "host-linux-amd64-bullseye-vmx",
all: add a macOS 10.14 (Mojave) builder Fixes golang/go#27806 Change-Id: I576f563acb2c50cd0456cd4e6a1271b9aa59c9df Reviewed-on: https://go-review.googlesource.com/c/build/+/169498 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-27 02:04:31 +03:00
buildsRepo: disabledBuilder,
dashboard, buildlet: add a disabled builder with nested virt, for testing This adds a linux-amd64 COS builder that should be just like our existing linux-amd64 COS builder except that it's using a forked image that has the VMX license bit enabled for nested virtualization. (GCE appears to be using the license mechanism as some sort of opt-in mechanism for features that aren't yet GA; might go away?) Once this is in, it won't do any new builds as regular+trybot builders are disabled. But it means I can then use gomote + debugnewvm to work on preparing the other four image types. Updates golang/go#15581 (solaris) Updates golang/go#23060 (dragonfly) Updates golang/go#30262 (riscv) Updates golang/go#30267 (fuchsia) Updates golang/go#23824 (android) Change-Id: Ic55f17eea17908dba7f58618d8cd162a2ed9b015 Reviewed-on: https://go-review.googlesource.com/c/162959 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-02-16 01:05:42 +03:00
})
dashboard: reenable linux-amd64-alpine It passes all.bash in the main repo after CL 419995. For golang/go#19938. Change-Id: I03c32193bbc83667e7bbbb2251e15a4a9bef6cfc Reviewed-on: https://go-review.googlesource.com/c/build/+/420214 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 19:16:23 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-alpine",
HostType: "host-linux-amd64-alpine",
build: restrict alpine builder to main branch Require Go 1.20 for alpine builder (no need to test 1.19/1.18 with this builder at the moment). Change-Id: I36d2bc86aab5c4ef04203baa840c27d984af9d0d Reviewed-on: https://go-review.googlesource.com/c/build/+/422094 Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-08 21:41:35 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return atLeastGo1(goBranch, 20) && buildRepoByDefault(repo)
},
dashboard: reenable linux-amd64-alpine It passes all.bash in the main repo after CL 419995. For golang/go#19938. Change-Id: I03c32193bbc83667e7bbbb2251e15a4a9bef6cfc Reviewed-on: https://go-review.googlesource.com/c/build/+/420214 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 19:16:23 +03:00
})
dashboard: remove alpine builder It's doing no good being red all the time, especially as nobody is working on it. Updates golang/go#22689 Updates golang/go#19938 Change-Id: Icb947878d85e920f24ea458eb0f319844ca5bd60 Reviewed-on: https://go-review.googlesource.com/78575 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-11-18 06:31:35 +03:00
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
// addMiscCompileGo1 adds a misc-compile TryBot that
// runs buildall.bash on the specified target(s), up to 3 max.
// The targets are matched against the "go tool dist list" name,
// but with hyphens instead of forward slashes ("linux-amd64", etc).
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
// If min is non-zero, it specifies the minimum Go 1.x version.
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
addMiscCompileGo1 := func(min int, suffix string, targets ...string) {
if len(targets) > 3 {
// This limit will do until we have better visibility
// into holistic TryBot completion times via metrics.
panic("at most 3 targets may be specified to avoid making TryBots slow; see issues 32632 and 17104")
}
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
var v types.MajorMinor
var alsoNote string
if min != 0 {
dashboard: fix vet warning Fix warning reported by "go vet": ./builders.go:1126:11: golang.org/x/build/types.MajorMinor struct literal uses unkeyed fields ./builders.go:1506:8: golang.org/x/build/types.MajorMinor struct literal uses unkeyed fields Change-Id: Ifa167bdcda4eb6123362353da58307dfb94174df Reviewed-on: https://go-review.googlesource.com/c/build/+/423034 Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-08-11 21:12:53 +03:00
v = types.MajorMinor{Major: 1, Minor: min}
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
alsoNote = fmt.Sprintf(" Applies to Go 1.%d and newer.", min)
}
cmd/coordinator: shard the misc-compile builder over 4 builders Now that it's on Kubernetes, it's fast and cheap to shard it wider. Change-Id: I2858f4c417ef26661575a348fbfc47f4c25d81a2 Reviewed-on: https://go-review.googlesource.com/22795 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-05-05 03:42:49 +03:00
addBuilder(BuildConfig{
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
Name: "misc-compile" + suffix,
dashboard/builders: upgrade non-specific Linux builders to Stretch We have to update the non-versioned builders sometime, and now seems as good as any. This is just an easy first step, still need to figure out vmx and whether to disable the stretch builders on master/1.20. For golang/go#56414. Change-Id: I7f1ce4faa9c6fa1595b7a0c3c72d451b1d18e5f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/445616 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-26 20:52:15 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
tryBot: defaultTrySet(),
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
},
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
tryOnly: true,
MinimumGoVersion: v,
CompileOnly: true,
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
Notes: "Runs buildall.bash to cross-compile & vet std+cmd packages for " + strings.Join(targets, " & ") + ", but doesn't run any tests." + alsoNote,
cmd/coordinator: shard the misc-compile builder over 4 builders Now that it's on Kubernetes, it's fast and cheap to shard it wider. Change-Id: I2858f4c417ef26661575a348fbfc47f4c25d81a2 Reviewed-on: https://go-review.googlesource.com/22795 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-05-05 03:42:49 +03:00
allScriptArgs: []string{
// Filtering pattern to buildall.bash:
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
"^(" + strings.Join(targets, "|") + ")$",
cmd/coordinator: shard the misc-compile builder over 4 builders Now that it's on Kubernetes, it's fast and cheap to shard it wider. Change-Id: I2858f4c417ef26661575a348fbfc47f4c25d81a2 Reviewed-on: https://go-review.googlesource.com/22795 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-05-05 03:42:49 +03:00
},
})
}
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
// addMiscCompile adds a misc-compile TryBot
// for all supported Go versions.
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
addMiscCompile := func(suffix string, targets ...string) { addMiscCompileGo1(0, suffix, targets...) }
// Arrange so that no more than 3 ports are tested sequentially in each misc-compile
// TryBot to avoid any individual misc-compile TryBot from becoming a bottleneck for
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// overall TryBot completion time (currently 10 minutes; see go.dev/issue/17104).
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
//
// The TestTryBotsCompileAllPorts test is used to detect any gaps in TryBot coverage
// when new ports are added, and the misc-compile pairs below can be re-arranged.
//
// (In the past, we used flexible regexp patterns that matched all architectures
// for a given GOOS value. However, over time as new architectures were added,
// some misc-compile TryBot could become much slower than others.)
//
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// See go.dev/issue/32632.
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
addMiscCompile("-windows-arm", "windows-arm", "windows-arm64")
addMiscCompile("-darwin", "darwin-amd64", "darwin-arm64")
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
addMiscCompile("-mips", "linux-mips", "linux-mips64")
addMiscCompile("-mipsle", "linux-mipsle", "linux-mips64le")
addMiscCompile("-ppc", "linux-ppc64", "linux-ppc64le", "aix-ppc64")
addMiscCompile("-freebsd", "freebsd-386", "freebsd-arm", "freebsd-arm64")
addMiscCompile("-netbsd", "netbsd-386", "netbsd-amd64")
addMiscCompile("-netbsd-arm", "netbsd-arm", "netbsd-arm64")
addMiscCompile("-openbsd", "openbsd-386", "openbsd-mips64")
addMiscCompile("-openbsd-arm", "openbsd-arm", "openbsd-arm64")
addMiscCompile("-plan9", "plan9-386", "plan9-amd64", "plan9-arm")
dashboard: add loong64 slowbot alias and misc-compile trybot misc-compile builders are limited to 3 ports each. Since both of the other builders are full, move the solaris/illumos ports to a new builder to make room in other-1. For golang/go#46229. Change-Id: Ifbf08679ea19252b500d1b8413ce5d95363366a1 Reviewed-on: https://go-review.googlesource.com/c/build/+/407507 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-05-20 20:51:15 +03:00
addMiscCompile("-solaris", "solaris-amd64", "illumos-amd64")
addMiscCompile("-other-1", "dragonfly-amd64", "linux-loong64")
dashboard: include at most 3 ports per misc-compile TryBot Between Go 1.15, 1.16 and tip, the following 29 ports don't have a real TryBot and instead rely on misc-compile TryBots for their pre-submit coverage: • aix/ppc64 • darwin/amd64 • darwin/arm64 • dragonfly/amd64 • freebsd/386 • freebsd/arm • freebsd/arm64 • illumos/amd64 • linux/mips • linux/mips64 • linux/mipsle • linux/mips64le • linux/ppc64 • linux/ppc64le • linux/riscv64 • linux/s390x • netbsd/386 • netbsd/amd64 • netbsd/arm • netbsd/arm64 • openbsd/386 • openbsd/arm • openbsd/arm64 • openbsd/mips64 • plan9/386 • plan9/amd64 • plan9/arm • solaris/amd64 • windows/arm The previous approach for misc-compile target selection was to break them up primarily by GOOS value. However, as new architectures were added over time, some misc-compile TryBots got to a point where they were testing upwards of 5 ports (for example, misc-compile-openbsd was testing 386, amd64, arm, arm64, and mips64 architectures). Since each port is tested sequentially, allocating too many to one misc-compile TryBot can cause it to become the bottleneck of an entire TryBot run, exceeding the 10 minute completion time goal. Arrange it so misc-compile TryBot target selection is done explicitly in x/build, and pick 3 as max number of targets per TryBot for now. Based on recent timing observations, that should strike a decent balance between resource use (spinning up a builder) vs chance of a misc-compile TryBot becoming a bottleneck. It will also give us an opportunity to compare timing of 1, 2 and 3 targets per misc-compile in the future. (When we start tracking timing for TryBot completion time holistically, we'll be in a better position to refine this strategy further.) Making misc-compile target selection explicit in x/build also enables removing unnecessary duplicate misc-compile coverage from ports that already have a real TryBot (for example, openbsd/amd64 was previously tested via both the openbsd-amd64-68 TryBot and misc-compile-openbsd). This shouldn't be needed, so it's no longer done. For golang/go#17104. Fixes golang/go#32632. Change-Id: Iac918377b91af3e48780b38ffdf3153e213eeba2 Reviewed-on: https://go-review.googlesource.com/c/build/+/313210 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-04-23 23:56:37 +03:00
addMiscCompile("-other-2", "linux-riscv64", "linux-s390x", "linux-arm-arm5") // 'linux-arm-arm5' is linux/arm with GOARM=5.
dashboard: add freebsd-riscv64 to misc compile Update golang/go#53466 Change-Id: I26b0fa92343779e2dd7c872cf587f86c7db4b09b Reviewed-on: https://go-review.googlesource.com/c/build/+/438335 Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-04 06:27:02 +03:00
addMiscCompileGo1(20, "-go1.20", "freebsd-riscv64")
dashboard: remove misc-compile-ios builder Since sending CL 257617, I've learned that iOS was never a supported target for misc-compile. It was always filtered out unconditionally in GOROOT/src/buildall.bash, and the comment suggesting that we test iOS targets was inaccurate. Remove the naive misc-compile-ios builder since it's not expected to start working soon, and update misc-builder architecture filtering code and comments to match the current reality better. After this change, it will be viable to remove mobile target filtering from GOROOT/src/buildall.bash. If that's done, then x/build/dashboard will become a centralized place for all misc-builder target selection. Ignore darwin-arm in TestTryBotsCompileAllPorts so the test doesn't fail when executed with Go 1.14. Not having that builder is intended. For golang/go#41610. Updates golang/go#25963. Change-Id: Ic6f5dc95edb67f8e6ebc0a77979e55eb0cc325cb Reviewed-on: https://go-review.googlesource.com/c/build/+/258057 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-09-28 18:04:35 +03:00
// TODO: Issue 25963, get the misc-compile trybots for Android/iOS.
// Then consider subrepos too, so "mobile" can at least be included
// as a misc-compile for ^android- and ^ios-.
cmd/coordinator: shard the misc-compile builder over 4 builders Now that it's on Kubernetes, it's fast and cheap to shard it wider. Change-Id: I2858f4c417ef26661575a348fbfc47f4c25d81a2 Reviewed-on: https://go-review.googlesource.com/22795 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-05-05 03:42:49 +03:00
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-amd64-nocgo",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Notes: "cgo disabled",
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b := buildRepoByDefault(repo)
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
switch repo {
case "perf":
// Requires sqlite, which requires cgo.
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b = false
case "exp":
b = true
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
}
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
return b
dashboard: add some "exp" trybots back, clean up some config Fixes golang/go#30781 Change-Id: I2672ca2949837c3cfe8fa6bd8011d1b9b43cca03 Reviewed-on: https://go-review.googlesource.com/c/build/+/167640 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-03-14 23:35:32 +03:00
},
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
env: []string{
"CGO_ENABLED=0",
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
// This USER=root was required for Docker-based builds but probably isn't required
// in the VM anymore, since the buildlet probably already has this in its environment.
// (It was required because without cgo, it couldn't find the username)
"USER=root",
},
})
addBuilder(BuildConfig{
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
Name: "linux-amd64-noopt",
Notes: "optimizations and inlining disabled",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
buildsRepo: onlyGo,
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
"GO_GCFLAGS=-N -l",
},
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
})
dashboard: add SSA check builder Now that SSA checks are off by default, let's run a builder with the checks on just to make sure they keep passing. Change-Id: I7edd2a2865681a135ccf755be7a14f8645c0a8aa Reviewed-on: https://go-review.googlesource.com/20882 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-03-19 01:30:38 +03:00
addBuilder(BuildConfig{
build: move Linux and nacl builders to Kubernetes, add ssacheck trybot And shard the nacl builders. Fixes golang/go#15242 Fixes golang/go#12546 Change-Id: I3311678dbb64a76026f75f5691cffac0f25d976b Reviewed-on: https://go-review.googlesource.com/22780 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Ross Light <light@google.com>
2016-05-04 20:47:12 +03:00
Name: "linux-amd64-ssacheck",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
buildsRepo: onlyGo,
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
tryBot: nil, // TODO: add a func to conditionally run this trybot if compiler dirs are touched
build: move Linux and nacl builders to Kubernetes, add ssacheck trybot And shard the nacl builders. Fixes golang/go#15242 Fixes golang/go#12546 Change-Id: I3311678dbb64a76026f75f5691cffac0f25d976b Reviewed-on: https://go-review.googlesource.com/22780 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Ross Light <light@google.com>
2016-05-04 20:47:12 +03:00
CompileOnly: true,
Notes: "SSA internal checks enabled",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
"GO_GCFLAGS=-d=ssa/check/on,dclstack",
},
dashboard: add SSA check builder Now that SSA checks are off by default, let's run a builder with the checks on just to make sure they keep passing. Change-Id: I7edd2a2865681a135ccf755be7a14f8645c0a8aa Reviewed-on: https://go-review.googlesource.com/20882 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-03-19 01:30:38 +03:00
})
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
addBuilder(BuildConfig{
dashboard: unset known issue for staticlockranking builder CL 207619 has been submitted to master, fixing golang.org/issue/38029. The linux-amd64-staticlockranking builder has been passing since then. Unset its known issue so that if there are regressions in the future, they can be investigated. For golang/go#38029. For golang/go#37937. Change-Id: I0de8e4ac122effee56aac73c741fab41512ff0c2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227544 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dan Scales <danscales@google.com>
2020-04-08 19:13:38 +03:00
Name: "linux-amd64-staticlockranking",
dashboard/builders: upgrade non-specific Linux builders to Stretch We have to update the non-versioned builders sometime, and now seems as good as any. This is just an easy first step, still need to figure out vmx and whether to disable the stretch builders on master/1.20. For golang/go#56414. Change-Id: I7f1ce4faa9c6fa1595b7a0c3c72d451b1d18e5f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/445616 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-26 20:52:15 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
Notes: "builder with GOEXPERIMENT=staticlockranking, see go.dev/issue/37937",
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
return repo == "go"
dashboard: add linux-amd64-staticlockranking builder This is a new linux/amd64 GCE builder for the purpose of testing the GOEXPERIMENT=staticlockranking configuration which is landing to master branch soon. It runs only on the main Go repository master branch and release branches 1.15 and newer. No golang.org/x repos. Not included in trybots by default, but can be requested via SlowBots by saying TRY=linux-amd64-staticlockranking. Also expand documentation of BuildConfig.buildsRepo field to make it more clear how to use it. A common mistake for custom buildsRepo functions that are added is to create a custom policy with a minor adjustment and forgetting to preserve the rest of the default build repo policy. Fixes golang/go#37937 Change-Id: Ic56f82e9ede30cb6fe8f6cc7d0282d6a0a12c1b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/224078 Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-03-19 17:34:11 +03:00
},
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
"GOEXPERIMENT=staticlockranking",
},
})
dashboard: add linux-amd64-unified builder This adds a trybot+builder for testing cmd/compile's unified IR construction experiment on the dev.typeparams branch. Fixes golang/go#46786. Change-Id: Ibf3d5ab7a727c52cf13486798e02077faa08e2b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/328891 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-17 09:08:22 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-unified",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-buster",
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
Notes: "builder with GOEXPERIMENT=unified, see go.dev/issue/46786",
dashboard: add linux-amd64-unified builder This adds a trybot+builder for testing cmd/compile's unified IR construction experiment on the dev.typeparams branch. Fixes golang/go#46786. Change-Id: Ibf3d5ab7a727c52cf13486798e02077faa08e2b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/328891 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-17 09:08:22 +03:00
tryBot: func(repo, branch, goBranch string) bool {
dashboard: disable tools repo trybot for unified IR builder x/tools has a bunch of tests that don't currently work with GOEXPERIMENT=unified. This is a known issue that's going to take some time to fix, so let's just disable the trybot for now to prevent blocking other developers. Updates golang/go#52150. Change-Id: I3fa3ee406a422a4b01cf1ce7753a27be83516f10 Reviewed-on: https://go-review.googlesource.com/c/build/+/398874 Trust: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Trust: Matthew Dempsky <mdempsky@google.com>
2022-04-06 04:28:28 +03:00
// TODO(go.dev/issue/52150): Restore testing against tools repo.
dashboard: enable unified/nounified builders for dev.unified There's now the dev.unified branch for handling Unified IR development, so have the unified (and nounified) trybot and builders testing that branch instead of dev.typeparams (which is inactive). Change-Id: Ib6911ee68b4c570e34fe282bb7a27c571b70e3e0 Reviewed-on: https://go-review.googlesource.com/c/build/+/410634 Run-TryBot: Matthew Dempsky <mdempsky@google.com> Auto-Submit: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-06-06 19:34:13 +03:00
return (repo == "go" /*|| repo == "tools"*/) && (goBranch == "master" || goBranch == "dev.unified")
dashboard: add linux-amd64-unified builder This adds a trybot+builder for testing cmd/compile's unified IR construction experiment on the dev.typeparams branch. Fixes golang/go#46786. Change-Id: Ibf3d5ab7a727c52cf13486798e02077faa08e2b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/328891 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-17 09:08:22 +03:00
},
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: enable unified/nounified builders for dev.unified There's now the dev.unified branch for handling Unified IR development, so have the unified (and nounified) trybot and builders testing that branch instead of dev.typeparams (which is inactive). Change-Id: Ib6911ee68b4c570e34fe282bb7a27c571b70e3e0 Reviewed-on: https://go-review.googlesource.com/c/build/+/410634 Run-TryBot: Matthew Dempsky <mdempsky@google.com> Auto-Submit: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-06-06 19:34:13 +03:00
return (repo == "go" || repo == "tools") && (goBranch == "master" || goBranch == "dev.unified")
dashboard: add linux-amd64-unified builder This adds a trybot+builder for testing cmd/compile's unified IR construction experiment on the dev.typeparams branch. Fixes golang/go#46786. Change-Id: Ibf3d5ab7a727c52cf13486798e02077faa08e2b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/328891 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-17 09:08:22 +03:00
},
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
"GOEXPERIMENT=unified",
},
numTestHelpers: 1,
numTryTestHelpers: 4,
dashboard: add known issue for linux-amd64-unified For golang/go#52653. Updates golang/go#52150. Change-Id: Ie76101e2a790b77c85a89fe41f4069f8cdd1522d Reviewed-on: https://go-review.googlesource.com/c/build/+/408699 Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-05-26 18:27:45 +03:00
KnownIssues: []int{52150},
dashboard: add linux-amd64-nounified builder This builder is identical to the current linux-amd64-unified builder config, except it sets GOEXPERIMENT=nounified instead to ensure we maintain coverage after switching the default mode. Fixes golang/go#51397. Change-Id: If0ffbf251337db3addce61618784501c7a20283f Reviewed-on: https://go-review.googlesource.com/c/build/+/388494 Trust: Matthew Dempsky <mdempsky@google.com> Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-28 22:43:03 +03:00
})
addBuilder(BuildConfig{
Name: "linux-amd64-nounified",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-buster",
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
Notes: "builder with GOEXPERIMENT=nounified, see go.dev/issue/51397",
dashboard: add linux-amd64-nounified builder This builder is identical to the current linux-amd64-unified builder config, except it sets GOEXPERIMENT=nounified instead to ensure we maintain coverage after switching the default mode. Fixes golang/go#51397. Change-Id: If0ffbf251337db3addce61618784501c7a20283f Reviewed-on: https://go-review.googlesource.com/c/build/+/388494 Trust: Matthew Dempsky <mdempsky@google.com> Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-28 22:43:03 +03:00
tryBot: func(repo, branch, goBranch string) bool {
dashboard: enable unified/nounified builders for dev.unified There's now the dev.unified branch for handling Unified IR development, so have the unified (and nounified) trybot and builders testing that branch instead of dev.typeparams (which is inactive). Change-Id: Ib6911ee68b4c570e34fe282bb7a27c571b70e3e0 Reviewed-on: https://go-review.googlesource.com/c/build/+/410634 Run-TryBot: Matthew Dempsky <mdempsky@google.com> Auto-Submit: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-06-06 19:34:13 +03:00
return (repo == "go" || repo == "tools") && (goBranch == "master" || goBranch == "dev.unified")
dashboard: add linux-amd64-nounified builder This builder is identical to the current linux-amd64-unified builder config, except it sets GOEXPERIMENT=nounified instead to ensure we maintain coverage after switching the default mode. Fixes golang/go#51397. Change-Id: If0ffbf251337db3addce61618784501c7a20283f Reviewed-on: https://go-review.googlesource.com/c/build/+/388494 Trust: Matthew Dempsky <mdempsky@google.com> Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-28 22:43:03 +03:00
},
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: enable unified/nounified builders for dev.unified There's now the dev.unified branch for handling Unified IR development, so have the unified (and nounified) trybot and builders testing that branch instead of dev.typeparams (which is inactive). Change-Id: Ib6911ee68b4c570e34fe282bb7a27c571b70e3e0 Reviewed-on: https://go-review.googlesource.com/c/build/+/410634 Run-TryBot: Matthew Dempsky <mdempsky@google.com> Auto-Submit: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-06-06 19:34:13 +03:00
return (repo == "go" || repo == "tools") && (goBranch == "master" || goBranch == "dev.unified")
dashboard: add linux-amd64-nounified builder This builder is identical to the current linux-amd64-unified builder config, except it sets GOEXPERIMENT=nounified instead to ensure we maintain coverage after switching the default mode. Fixes golang/go#51397. Change-Id: If0ffbf251337db3addce61618784501c7a20283f Reviewed-on: https://go-review.googlesource.com/c/build/+/388494 Trust: Matthew Dempsky <mdempsky@google.com> Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Robert Findley <rfindley@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-28 22:43:03 +03:00
},
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
"GOEXPERIMENT=nounified",
},
numTestHelpers: 1,
numTryTestHelpers: 4,
dashboard: add linux-amd64-unified builder This adds a trybot+builder for testing cmd/compile's unified IR construction experiment on the dev.typeparams branch. Fixes golang/go#46786. Change-Id: Ibf3d5ab7a727c52cf13486798e02077faa08e2b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/328891 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-17 09:08:22 +03:00
})
dashboard: add linux-amd64-goamd64v3 builder The purpose of this builder will be to test Go with a non-default value of the new GOAMD64 environment variable. For golang/go#48505. Updates golang/go#45453. Change-Id: Ic7bf0bd45f3539530ac6540cc3609f87cfdab6f7 Reviewed-on: https://go-review.googlesource.com/c/build/+/386116 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Trust: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-16 09:05:35 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-goamd64v3",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: add linux-amd64-goamd64v3 builder The purpose of this builder will be to test Go with a non-default value of the new GOAMD64 environment variable. For golang/go#48505. Updates golang/go#45453. Change-Id: Ic7bf0bd45f3539530ac6540cc3609f87cfdab6f7 Reviewed-on: https://go-review.googlesource.com/c/build/+/386116 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Trust: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-16 09:05:35 +03:00
Notes: "builder with GOAMD64=v3, see proposal 45453 and issue 48505",
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
"GOAMD64=v3",
},
})
dashboard, cmd/coordinator: add -racecompile builder Change-Id: Idc5756f82081de6b5dfd17036f2bfc9cf11c5659 Reviewed-on: https://go-review.googlesource.com/41414 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-22 02:41:12 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-racecompile",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
tryBot: nil, // TODO: add a func to conditionally run this trybot if compiler dirs are touched
dashboard, cmd/coordinator: add -racecompile builder Change-Id: Idc5756f82081de6b5dfd17036f2bfc9cf11c5659 Reviewed-on: https://go-review.googlesource.com/41414 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-22 02:41:12 +03:00
CompileOnly: true,
cmd/coordinator: make linux-amd64-racecompile rebuild std/cmd with -c=128 Updates golang/go#19962 Change-Id: I8b938a39b33d4e6b9b8dc5bc0802da95e889ee46 Reviewed-on: https://go-review.googlesource.com/41613 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-25 00:14:05 +03:00
SkipSnapshot: true,
StopAfterMake: true,
dashboard: use race-enabled linker in racecompile builder When the compiler's backend became concurrent, we introduced the racecompile builder to run the compiler with the race detector enabled to catch races. In the new linker work the linker will become more concurrent as well. It is probably a good idea to run the linker with the race detector as well. Change-Id: Ib50f030cba0509730714b74462f5a8942fe2fd2d Reviewed-on: https://go-review.googlesource.com/c/build/+/226369 Run-TryBot: Cherry Zhang <cherryyz@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-03-30 18:20:59 +03:00
InstallRacePackages: []string{"cmd/compile", "cmd/link"},
Notes: "race-enabled cmd/compile and cmd/link",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
},
dashboard, cmd/coordinator: add -racecompile builder Change-Id: Idc5756f82081de6b5dfd17036f2bfc9cf11c5659 Reviewed-on: https://go-review.googlesource.com/41414 Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com>
2017-04-22 02:41:12 +03:00
})
build: convert most Linux builders to be VM-based We still use Dockerfiles to describe them, but then a new tool (docker2boot) converts them into VM images suitable for booting on GCE, running the buildlet like all the other operating systems. Things are easier if everything acts the same way. Note that since we're no longer moving around Docker images, the image size and the layer accumulation cruft no longer matters. We can now have Dockerfile lines like "RUN rm -rf /usr/share/doc" and it actually results in a smaller VM image, since we just "docker export" the files out of it to create the VM image. This doesn't yet convert the clang, sid, or nacl builders. The coordinator still runs those under Docker directly. A future change will convert those to VM images as well. Change-Id: Iedb136ae3daf888c955eb843bdcc9a638d08f5e9 Reviewed-on: https://go-review.googlesource.com/3341 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-28 01:22:21 +03:00
addBuilder(BuildConfig{
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
Name: "linux-amd64-race",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
tryBot: defaultTrySet(),
dashboard: don't build x/build on so many builders It was kinda overkill. Change-Id: Ied7fc42aa59a1ed18cc1da20e51c8ed386d84629 Reviewed-on: https://go-review.googlesource.com/c/build/+/210378 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-12-07 08:14:28 +03:00
buildsRepo: defaultPlusExpBuild,
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: fasterTrybots,
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
numTestHelpers: 1,
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
numTryTestHelpers: 5,
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
env: []string{
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: enable outbound firewall on a few more Linux-based builders Updates golang/go#30612 Change-Id: Id472e753043976b8671c15491b82bb57e3804d95 Reviewed-on: https://go-review.googlesource.com/c/build/+/165638 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-06 08:20:12 +03:00
},
all: add env support, freebsd-386, freebsd-amd64-race, re-enable plan9 Update golang/go#9491 Update golang/go#8639 Change-Id: I1f43c751777f10a6d5870ca9bbb8c2a3430189bf Reviewed-on: https://go-review.googlesource.com/3170 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-22 02:15:48 +03:00
})
env: convert linux-x86-clang to be VM-based Change-Id: I583d751652dec9176169b4d4705f3813506017e3 Reviewed-on: https://go-review.googlesource.com/4790 Reviewed-by: Minux Ma <minux@golang.org>
2015-02-13 06:45:02 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-386-clang",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-clang",
dashboard, env/linux-x86-jessie: remove Debian jessie Debian jessie is out of LTS support. This change removes the Debian jessie based builders: - use linux-x86-stretch for the misc-compile builders. - linux-x86-jessie host has been removed. - documentation for the linux-x86-clang builders have been updated. - documentation throughout the repo has been updated. For golang/go#47721 Change-Id: Ia2e916ea94fe8e6adb8f5a56d6c7319817de75e2 Reviewed-on: https://go-review.googlesource.com/c/build/+/383154 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Trust: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-04 19:12:47 +03:00
Notes: "Debian Buster + clang 7.0 instead of gcc",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
env: []string{"CC=/usr/bin/clang", "GOHOSTARCH=386"},
env: convert linux-x86-clang to be VM-based Change-Id: I583d751652dec9176169b4d4705f3813506017e3 Reviewed-on: https://go-review.googlesource.com/4790 Reviewed-by: Minux Ma <minux@golang.org>
2015-02-13 06:45:02 +03:00
})
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-amd64-clang",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-clang",
dashboard, env/linux-x86-jessie: remove Debian jessie Debian jessie is out of LTS support. This change removes the Debian jessie based builders: - use linux-x86-stretch for the misc-compile builders. - linux-x86-jessie host has been removed. - documentation for the linux-x86-clang builders have been updated. - documentation throughout the repo has been updated. For golang/go#47721 Change-Id: Ia2e916ea94fe8e6adb8f5a56d6c7319817de75e2 Reviewed-on: https://go-review.googlesource.com/c/build/+/383154 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Trust: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-02-04 19:12:47 +03:00
Notes: "Debian Buster + clang 7.0 instead of gcc",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
env: []string{"CC=/usr/bin/clang"},
env: convert linux-x86-clang to be VM-based Change-Id: I583d751652dec9176169b4d4705f3813506017e3 Reviewed-on: https://go-review.googlesource.com/4790 Reviewed-by: Minux Ma <minux@golang.org>
2015-02-13 06:45:02 +03:00
})
env: update linux-x86-sid to be a VM Fixes #9873 Change-Id: I08c501ef52ebde4cdbc48fe45a5342488000c433 Reviewed-on: https://go-review.googlesource.com/4874 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-02-14 06:01:32 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-386-sid",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-sid",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Notes: "Debian sid (unstable)",
env: []string{"GOHOSTARCH=386"},
env: update linux-x86-sid to be a VM Fixes #9873 Change-Id: I08c501ef52ebde4cdbc48fe45a5342488000c433 Reviewed-on: https://go-review.googlesource.com/4874 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-02-14 06:01:32 +03:00
})
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-amd64-sid",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-sid",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Notes: "Debian sid (unstable)",
env: update linux-x86-sid to be a VM Fixes #9873 Change-Id: I08c501ef52ebde4cdbc48fe45a5342488000c433 Reviewed-on: https://go-review.googlesource.com/4874 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2015-02-14 06:01:32 +03:00
})
env/linux-x86-fedora: add Fedora builder Not using a Fedora kernel yet, but better than nothing. Updates golang/go#26796 Change-Id: I228442bf6606696407a8d3fbd098df59df7353e1 Reviewed-on: https://go-review.googlesource.com/c/build/+/175999 Reviewed-by: Ian Lance Taylor <iant@golang.org>
2019-05-08 19:25:38 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-amd64-fedora",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-fedora",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Notes: "Fedora",
env/linux-x86-fedora: add Fedora builder Not using a Fedora kernel yet, but better than nothing. Updates golang/go#26796 Change-Id: I228442bf6606696407a8d3fbd098df59df7353e1 Reviewed-on: https://go-review.googlesource.com/c/build/+/175999 Reviewed-by: Ian Lance Taylor <iant@golang.org>
2019-05-08 19:25:38 +03:00
})
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-androidemu",
dashboard: rename host-android-amd64-emu to host-linux-amd64-androidemu This follows the name convention and avoids a HostArch line. For golang/go#44505. Change-Id: I14654e64751ee830101e1191bd44cd426b3ecce2 Reviewed-on: https://go-review.googlesource.com/c/build/+/420804 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-08-03 22:43:12 +03:00
HostType: "host-linux-amd64-androidemu",
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
env: []string{
"GOARCH=amd64",
"GOOS=linux",
"CGO_ENABLED=1",
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
},
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
tryBot: func(repo, branch, goBranch string) bool {
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
// Only for mobile repo for now, not "go":
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
return repo == "mobile" && branch == "master" && goBranch == "master"
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
},
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return repo == "mobile" && branch == "master" && goBranch == "master"
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
},
Notes: "Runs GOOS=linux but with the Android emulator attached, for running x/mobile host tests.",
})
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
addBuilder(BuildConfig{
dashboard: enable linux-amd64-stretch builder The builder named "linux-amd64" was updated from Stretch to Bullseye in CL 343633, so it's worthwhile for the linux-amd64-stretch builder to be running post-submit builds. Updates golang/go#47721. Change-Id: I5d42af77771789724a5e6ffdc9260ab15e845752 Reviewed-on: https://go-review.googlesource.com/c/build/+/386114 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-02-16 08:06:34 +03:00
Name: "linux-amd64-stretch",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-stretch",
dashboard: enable linux-amd64-stretch builder The builder named "linux-amd64" was updated from Stretch to Bullseye in CL 343633, so it's worthwhile for the linux-amd64-stretch builder to be running post-submit builds. Updates golang/go#47721. Change-Id: I5d42af77771789724a5e6ffdc9260ab15e845752 Reviewed-on: https://go-review.googlesource.com/c/build/+/386114 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-02-16 08:06:34 +03:00
Notes: "Debian Stretch.",
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
dashboard/builders: disable Stretch builders on master/1.20 Stretch was EOL at the beginning of the 1.20 cycle, so according to our draft policy we should no longer build on it. For golang/go#56414. Change-Id: Ibac0d5438cf9e0b8f24cde7b38bb3f6cdc7a5096 Reviewed-on: https://go-review.googlesource.com/c/build/+/445618 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-10-26 21:07:00 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard/builders: don't run mobile on Stretch builders, clean up I forgot to check buildRepoByDefault on the Stretch builders, so they started running x/mobile. Also noticed a ton of obsolete builders/checks, clean them out while I'm at it. In the tests, clear out very old version checks, and replace "arbitrary release branch" versions with go1.99 rather than whatever happened to be current when the test case was written. For golang/go#56414. Change-Id: I88eeeaec5d166d1ac1a3938dbc26870ff8d4b33a Reviewed-on: https://go-review.googlesource.com/c/build/+/446183 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-28 21:17:45 +03:00
return atMostGo1(goBranch, 19) && buildRepoByDefault(repo) // Stretch was EOL at the start of the 1.20 cycle.
dashboard/builders: disable Stretch builders on master/1.20 Stretch was EOL at the beginning of the 1.20 cycle, so according to our draft policy we should no longer build on it. For golang/go#56414. Change-Id: Ibac0d5438cf9e0b8f24cde7b38bb3f6cdc7a5096 Reviewed-on: https://go-review.googlesource.com/c/build/+/445618 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-10-26 21:07:00 +03:00
},
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
})
env/linux-x86-bullseye, dashboard: add Debian Bullseye builder This change adds the host-linux-bullseye host as well as the configuration for the host. The linux-amd64-bullseye builder has been added in this change as well. Fixes golang/go#47720 Change-Id: I607f937133a0db3ed6a841f53dc7fef5e310a5a4 Reviewed-on: https://go-review.googlesource.com/c/build/+/342630 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-08-16 22:35:39 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-bullseye",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
env/linux-x86-bullseye, dashboard: add Debian Bullseye builder This change adds the host-linux-bullseye host as well as the configuration for the host. The linux-amd64-bullseye builder has been added in this change as well. Fixes golang/go#47720 Change-Id: I607f937133a0db3ed6a841f53dc7fef5e310a5a4 Reviewed-on: https://go-review.googlesource.com/c/build/+/342630 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-08-16 22:35:39 +03:00
Notes: "Debian Bullseye.",
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
})
env/linux-x86-buster: add Debian Buster builder This change adds a Debian Buster builder. Fixes golang/go#42410 Change-Id: If11ebe6df3bad88aac40b0a6f841edc5fb3a5b4a Reviewed-on: https://go-review.googlesource.com/c/build/+/267937 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-11-02 23:11:10 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-buster",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-buster",
env/linux-x86-buster: add Debian Buster builder This change adds a Debian Buster builder. Fixes golang/go#42410 Change-Id: If11ebe6df3bad88aac40b0a6f841edc5fb3a5b4a Reviewed-on: https://go-review.googlesource.com/c/build/+/267937 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-11-02 23:11:10 +03:00
Notes: "Debian Buster.",
env: []string{
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
})
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
addBuilder(BuildConfig{
Name: "linux-386-stretch",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-stretch",
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
Notes: "Debian Stretch, 32-bit builder.",
env: []string{
"GOARCH=386",
"GOHOSTARCH=386",
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
dashboard/builders: disable Stretch builders on master/1.20 Stretch was EOL at the beginning of the 1.20 cycle, so according to our draft policy we should no longer build on it. For golang/go#56414. Change-Id: Ibac0d5438cf9e0b8f24cde7b38bb3f6cdc7a5096 Reviewed-on: https://go-review.googlesource.com/c/build/+/445618 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-10-26 21:07:00 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard/builders: don't run mobile on Stretch builders, clean up I forgot to check buildRepoByDefault on the Stretch builders, so they started running x/mobile. Also noticed a ton of obsolete builders/checks, clean them out while I'm at it. In the tests, clear out very old version checks, and replace "arbitrary release branch" versions with go1.99 rather than whatever happened to be current when the test case was written. For golang/go#56414. Change-Id: I88eeeaec5d166d1ac1a3938dbc26870ff8d4b33a Reviewed-on: https://go-review.googlesource.com/c/build/+/446183 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-28 21:17:45 +03:00
return atMostGo1(goBranch, 19) && buildRepoByDefault(repo) // Stretch was EOL at the start of the 1.20 cycle.
dashboard/builders: disable Stretch builders on master/1.20 Stretch was EOL at the beginning of the 1.20 cycle, so according to our draft policy we should no longer build on it. For golang/go#56414. Change-Id: Ibac0d5438cf9e0b8f24cde7b38bb3f6cdc7a5096 Reviewed-on: https://go-review.googlesource.com/c/build/+/445618 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-10-26 21:07:00 +03:00
},
cmd/release, dashboard: implement builder plan for Go 1.16 See https://golang.org/issues/40561#issuecomment-731482962 for the plan description and rationale. Add new builder definitions that are needed for the plan. Don't rely on generic builder name like "linux-amd64" to avoid a repeat of golang.org/issue/31293; use a specific builder name instead. Remove support and test cases for Go 1.13, it's unsupported per release policy. For golang/go#40561. Change-Id: I070744e15be9f1932d649a27ee7e4599e467553f Reviewed-on: https://go-review.googlesource.com/c/build/+/276034 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-08 06:31:50 +03:00
})
dashboard: update Debian version for 386 builders This change updates various linux-386 builders after the release of bullseye: - linux-386 has been updated to bullseye. - linux-386-jessie has had the notes updated. - linux-386-buster has been added. Updates golang/go#47721 Change-Id: Iab0048fcad4d51839013074a51ad37b424d3a7af Reviewed-on: https://go-review.googlesource.com/c/build/+/343632 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-19 00:45:09 +03:00
addBuilder(BuildConfig{
Name: "linux-386-buster",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-buster",
dashboard: update Debian version for 386 builders This change updates various linux-386 builders after the release of bullseye: - linux-386 has been updated to bullseye. - linux-386-jessie has had the notes updated. - linux-386-buster has been added. Updates golang/go#47721 Change-Id: Iab0048fcad4d51839013074a51ad37b424d3a7af Reviewed-on: https://go-review.googlesource.com/c/build/+/343632 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-19 00:45:09 +03:00
Notes: "Debian Buster, 32-bit builder.",
env: []string{
"GOARCH=386",
"GOHOSTARCH=386",
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
})
dashboard,internal/releasetargets: target Bullseye for Go 1.20 For golang/go#56414, golang/go#40561. Change-Id: If799e9ea7171d33acc57c53442ca33f51f803d3c Reviewed-on: https://go-review.googlesource.com/c/build/+/445619 Auto-Submit: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-10-26 21:14:22 +03:00
addBuilder(BuildConfig{
Name: "linux-386-bullseye",
HostType: "host-linux-amd64-bullseye",
Notes: "Debian Bullseye, 32-bit builder.",
env: []string{
"GOARCH=386",
"GOHOSTARCH=386",
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
})
dashboard: add "longtest" builder to run all tests, without -short mode Fixes golang/go#12508 Change-Id: I62e1e296f10c7622c1967a5530c4b0e07c136dfd Reviewed-on: https://go-review.googlesource.com/113436 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2018-05-16 22:50:39 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-amd64-longtest",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard, env/linux-x86-bullseye: use Debian bullseye for linux-longtest builders This change update the linux-[386|amd64]-longtest builders to use Debian bullseye. This Debian bullseye has been updated to include utilities required for cmd/go tests. Fixes golang/go#48802 Change-Id: I2884e8b81d71fc45c1405149bb08c98ddca821cd Reviewed-on: https://go-review.googlesource.com/c/build/+/384295 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-02-09 01:05:00 +03:00
Notes: "Debian Bullseye with go test -short=false",
dashboard: include longtest builders for trybots on release branches The goal of this test policy change is to decrease the chance of a Go repository release branch from getting into a state where some longtest post-submit builders are failing, as this will interfere with the ability to issue releases after golang/go#29252 is fixed. There are not that many CLs sent to release branches, so the extra latency caused by slower longtest builders being a part of trybots should not be very disruptive. For golang/go#37827. For golang/go#29252. Change-Id: I819b120bb7b763df4acf4583375cdb840793d323 Reviewed-on: https://go-review.googlesource.com/c/build/+/235338 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-05-27 01:19:05 +03:00
tryBot: func(repo, branch, goBranch string) bool {
onReleaseBranch := strings.HasPrefix(branch, "release-branch.")
return repo == "go" && onReleaseBranch // See issue 37827.
},
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
// Test all repos, ignoring buildRepoByDefault.
// For golang.org/x repos, don't test non-latest versions.
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
return repo == "go" || (branch == "master" && goBranch == "master")
},
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
needsGoProxy: true, // for cmd/go module tests
dashboard: increase TIMEOUT_SCALE to 2 for linux-amd64-longtest runtime tests take about 180s in long mode, too close to the timeout limit (180 seconds), and this is causing sporadic timeout failures like https://build.golang.org/log/cda568a39f396e3fee64778a475528be452632ed Bump up the builder's timeout by 2x. Fixes golang/go#25629 Change-Id: I77e0f86f0b236cb953457ebdcbfc5763c2c6d54b Reviewed-on: https://go-review.googlesource.com/115016 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-29 22:03:23 +03:00
env: []string{
dashboard: increase timeout scale for longtest builders, add more CPU Updates golang/go#25886 Change-Id: I5168e291ab77cbd3843bdc39e319a68dfa65aedd Reviewed-on: https://go-review.googlesource.com/c/build/+/167638 Reviewed-by: Russ Cox <rsc@golang.org>
2019-03-14 19:06:57 +03:00
"GO_TEST_TIMEOUT_SCALE=5", // give them lots of time
dashboard: increase TIMEOUT_SCALE to 2 for linux-amd64-longtest runtime tests take about 180s in long mode, too close to the timeout limit (180 seconds), and this is causing sporadic timeout failures like https://build.golang.org/log/cda568a39f396e3fee64778a475528be452632ed Bump up the builder's timeout by 2x. Fixes golang/go#25629 Change-Id: I77e0f86f0b236cb953457ebdcbfc5763c2c6d54b Reviewed-on: https://go-review.googlesource.com/115016 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-29 22:03:23 +03:00
},
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/42661.
dashboard: add "longtest" builder to run all tests, without -short mode Fixes golang/go#12508 Change-Id: I62e1e296f10c7622c1967a5530c4b0e07c136dfd Reviewed-on: https://go-review.googlesource.com/113436 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2018-05-16 22:50:39 +03:00
})
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-longtest-race",
HostType: "host-linux-amd64-bullseye",
Notes: "Debian Bullseye with the race detector enabled and go test -short=false",
buildsRepo: func(repo, branch, goBranch string) bool {
b := buildRepoByDefault(repo)
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
}
return b
},
needsGoProxy: true, // for cmd/go module tests
env: []string{
"GO_TEST_TIMEOUT_SCALE=5", // Inherited from the longtest builder.
},
dashboard: shard linux-amd64-longtest-race and windows-amd64-longtest-newcc builders Fixes golang/go#56907. Change-Id: Iede30e41588326d6922f95c7c2dc1e837d801cfc Reviewed-on: https://go-review.googlesource.com/c/build/+/452857 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 00:02:00 +03:00
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/56907.
dashboard: add linux-amd64-longtest-race builder This builder runs the longtest test with the race detector turned on to identify races in -short=false tests. Fixes golang/go#54630. Change-Id: I6fabaa43522a4294f3a23e98ae0f436d4cc153d8 Reviewed-on: https://go-review.googlesource.com/c/build/+/449196 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-10 01:12:41 +03:00
})
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
addBuilder(BuildConfig{
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Name: "linux-386-longtest",
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard, env/linux-x86-bullseye: use Debian bullseye for linux-longtest builders This change update the linux-[386|amd64]-longtest builders to use Debian bullseye. This Debian bullseye has been updated to include utilities required for cmd/go tests. Fixes golang/go#48802 Change-Id: I2884e8b81d71fc45c1405149bb08c98ddca821cd Reviewed-on: https://go-review.googlesource.com/c/build/+/384295 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-02-09 01:05:00 +03:00
Notes: "Debian Bullseye with go test -short=false; to get 32-bit coverage",
dashboard: include longtest builders for trybots on release branches The goal of this test policy change is to decrease the chance of a Go repository release branch from getting into a state where some longtest post-submit builders are failing, as this will interfere with the ability to issue releases after golang/go#29252 is fixed. There are not that many CLs sent to release branches, so the extra latency caused by slower longtest builders being a part of trybots should not be very disruptive. For golang/go#37827. For golang/go#29252. Change-Id: I819b120bb7b763df4acf4583375cdb840793d323 Reviewed-on: https://go-review.googlesource.com/c/build/+/235338 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-05-27 01:19:05 +03:00
tryBot: func(repo, branch, goBranch string) bool {
onReleaseBranch := strings.HasPrefix(branch, "release-branch.")
return repo == "go" && onReleaseBranch // See issue 37827.
},
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
b := buildRepoByDefault(repo)
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
dashboard: stop testing x/build on even more builders Follow up to CL 210378 after looking at: https://build.golang.org/?repo=golang.org%2fx%2fbuild Updates golang/go#30640 Change-Id: I81505a9ca2985ffa6e75922665b14ef4de2af860 Reviewed-on: https://go-review.googlesource.com/c/build/+/211100 Reviewed-by: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-12-12 20:43:59 +03:00
}
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
return b
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
},
needsGoProxy: true, // for cmd/go module tests
env: []string{
dashboard: set GO{,HOST}ARCH in linux-386-longtest builder The linux-386-longtest builder was added in CL 202479 with these environment variables unset, which caused the builder to run long tests for the linux/amd64 pair. Setting these to "386" makes the builder run long tests for linux/386 instead, which increases 32-bit test coverage as originally intended. For golang/go#29641. Change-Id: I9fbebc9e37e5f27f21d840d86006192daeaee8c5 Reviewed-on: https://go-review.googlesource.com/c/build/+/234520 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-05-19 02:34:15 +03:00
"GOARCH=386",
"GOHOSTARCH=386",
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
"GO_TEST_TIMEOUT_SCALE=5", // give them lots of time
},
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/42661.
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
})
env/js-wasm, dashboard: add start of a js-wasm builder Updates golang/go#18892 Change-Id: I4b16afe8f0ce74f6ecd022f8bca14ada94ab308f Reviewed-on: https://go-review.googlesource.com/112736 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-11 08:54:32 +03:00
addBuilder(BuildConfig{
dashboard: speed up js/wasm trybots We don't need to run all the tests in a trybot. Run just enough to get good coverage, without going over 5 minutes. Any regressions elsewhere will be caught by the build.golang.org (slower) runs. Change-Id: I32f1fc17681bfb509844d2bd35b05c950806d283 Reviewed-on: https://go-review.googlesource.com/121938 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-06-28 23:30:35 +03:00
Name: "js-wasm",
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
HostType: "host-linux-amd64-js-wasm",
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
tryBot: explicitTrySet("go"),
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b := buildRepoByDefault(repo)
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
switch repo {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
case "benchmarks", "debug", "perf", "talks", "tools", "tour", "website":
// Don't test these golang.org/x repos.
b = false
}
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
}
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
return b
dashboard: update some build policy Mostly some regressions (building too much) from the massive refactoring in CL 166218, but also some minor changes. See test updates. Change-Id: Ie30f51b425367f18a49764ac971e262131959bc8 Reviewed-on: https://go-review.googlesource.com/c/build/+/166557 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 07:20:46 +03:00
},
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
distTestAdjust: func(run bool, distTest string, isNormalTry bool) bool {
if isNormalTry {
dashboard: speed up js/wasm trybots We don't need to run all the tests in a trybot. Run just enough to get good coverage, without going over 5 minutes. Any regressions elsewhere will be caught by the build.golang.org (slower) runs. Change-Id: I32f1fc17681bfb509844d2bd35b05c950806d283 Reviewed-on: https://go-review.googlesource.com/121938 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-06-28 23:30:35 +03:00
if strings.Contains(distTest, "/internal/") ||
strings.Contains(distTest, "vendor/golang.org/x/arch") {
return false
}
switch distTest {
dashboard: re-enable cmd/go build test on js/wasm Most tests will be skipped anyway because 'go build' is not available. But this at least ensures cmd/go will build for js/wasm after https://go.dev/cl/433480 is submitted. For golang/go#54219 Change-Id: I5f9b647973e7ee9a5849e1ce2818986794edc2c4 Reviewed-on: https://go-review.googlesource.com/c/build/+/434235 Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Tobias Klauser <tobias.klauser@gmail.com>
2022-09-25 21:28:57 +03:00
case "nolibgcc:crypto/x509", "reboot":
dashboard: speed up js/wasm trybots We don't need to run all the tests in a trybot. Run just enough to get good coverage, without going over 5 minutes. Any regressions elsewhere will be caught by the build.golang.org (slower) runs. Change-Id: I32f1fc17681bfb509844d2bd35b05c950806d283 Reviewed-on: https://go-review.googlesource.com/121938 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-06-28 23:30:35 +03:00
return false
}
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: speed up js/wasm trybots We don't need to run all the tests in a trybot. Run just enough to get good coverage, without going over 5 minutes. Any regressions elsewhere will be caught by the build.golang.org (slower) runs. Change-Id: I32f1fc17681bfb509844d2bd35b05c950806d283 Reviewed-on: https://go-review.googlesource.com/121938 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-06-28 23:30:35 +03:00
},
dashboard: re-enable js/wasm test dir tests They were removed to make the build faster but they've let a few bugs slip by now. Re-enable. The 10 test shards adds 812 seconds of test time. Over 5 machines, that's 162.4 seconds each. Add another test shard to bring it down more. js-wasm trybots are currently at ~350 seconds, so we have some budget to get a bit slower and still be under 5 minutes. Updates golang/go#34768 Change-Id: Ic40c226d26e873227510e644756b0cc969151186 Reviewed-on: https://go-review.googlesource.com/c/build/+/200477 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-10 22:09:40 +03:00
numTryTestHelpers: 5,
env/js-wasm, dashboard: add start of a js-wasm builder Updates golang/go#18892 Change-Id: I4b16afe8f0ce74f6ecd022f8bca14ada94ab308f Reviewed-on: https://go-review.googlesource.com/112736 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-11 08:54:32 +03:00
env: []string{
"GOOS=js", "GOARCH=wasm", "GOHOSTOS=linux", "GOHOSTARCH=amd64",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/workdir/go/misc/wasm",
cmd/coordinator: follow module proxy redirects And because this uses new-in-Go1.13 http.Header.Clone, restrict all the files to Go 1.13+ and bump the Dockerfile Go version. Fixes golang/go#33928 Change-Id: I147cc4465e393d2c34e59c70edf65f3901a5e132 Reviewed-on: https://go-review.googlesource.com/c/build/+/192341 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-29 21:28:01 +03:00
"GO_DISABLE_OUTBOUND_NETWORK=1",
env/js-wasm, dashboard: add start of a js-wasm builder Updates golang/go#18892 Change-Id: I4b16afe8f0ce74f6ecd022f8bca14ada94ab308f Reviewed-on: https://go-review.googlesource.com/112736 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-11 08:54:32 +03:00
},
})
dashboard: add OpenBSD 6.8 builders This change builds on top of CL 268297, using the updated env script to build OpenBSD 6.8 images, and adding new builders that use them. This has been tested with cmd/debugnewvm on a recent Go tip commit, as well as Go 1.15.4 and 1.14.11 commits. It passed, although there were also some failures seen. Once the builder is added, we'll know the test results for a wider set of commits, and can decide how to proceed from there. Minimize the configuration to a bare minimum. Specifically, remove MinCPUPlatform since setting it "Intel Skylake" was found not to have a noticeable effect on the speed of the build compared to the zero value: # With MinCPUPlatform = "Intel Skylake": $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 17m8.308s # With a zero MinCPUPlatform value: $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 16m28.518s For golang/go#35712. Updates golang/go#42426. Change-Id: I517a85738a034a3a4074488ccecd4408a91a4a07 Reviewed-on: https://go-review.googlesource.com/c/build/+/269577 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-12 20:27:32 +03:00
addBuilder(BuildConfig{
dashboard: shard openbsd-amd64-68 TryBot also The goal in CL 279512 was to reduce numTryTestHelpers from 5 to 4, but it unintentionally set the field only in the 386 builder, not the amd64 one. This caused the amd64 OpenBSD TryBot to get very slow (20-25 minutes), making it very much a bottleneck for overall TryBot completion time. Also stop explicitly setting some fields in openbsd-amd64-62 builder that have no effect by now, to simplify configuration. For golang/go#17104. Updates golang/go#35712. Change-Id: I22823e4848cab65f11bde2a1cc70527929d0792d Reviewed-on: https://go-review.googlesource.com/c/build/+/279723 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-12-23 21:33:19 +03:00
Name: "openbsd-amd64-68",
HostType: "host-openbsd-amd64-68",
distTestAdjust: noTestDirAndNoReboot,
numTryTestHelpers: 4,
dashboard: add OpenBSD 6.8 builders This change builds on top of CL 268297, using the updated env script to build OpenBSD 6.8 images, and adding new builders that use them. This has been tested with cmd/debugnewvm on a recent Go tip commit, as well as Go 1.15.4 and 1.14.11 commits. It passed, although there were also some failures seen. Once the builder is added, we'll know the test results for a wider set of commits, and can decide how to proceed from there. Minimize the configuration to a bare minimum. Specifically, remove MinCPUPlatform since setting it "Intel Skylake" was found not to have a noticeable effect on the speed of the build compared to the zero value: # With MinCPUPlatform = "Intel Skylake": $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 17m8.308s # With a zero MinCPUPlatform value: $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 16m28.518s For golang/go#35712. Updates golang/go#42426. Change-Id: I517a85738a034a3a4074488ccecd4408a91a4a07 Reviewed-on: https://go-review.googlesource.com/c/build/+/269577 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-12 20:27:32 +03:00
})
addBuilder(BuildConfig{
dashboard: skip x/review on slow 32-bit builders x/review is fairly disk-intensive (it shells out to 'git'), and also mostly for use by Go contributors (a smaller subset of Go users in general). It frequently times out on two particular 32-bit builders. I don't think we particularly need the coverage from those two builders for this repo, so rather than trying to speed up the test or tweak the scale factors, let's just skip it. Fixes golang/go#49529 Fixes golang/go#49530 Change-Id: I8da1216ebdf9287ae78d52bb03187b65eb33c9ee Reviewed-on: https://go-review.googlesource.com/c/build/+/363495 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-11 23:45:01 +03:00
Name: "openbsd-386-68",
HostType: "host-openbsd-386-68",
buildsRepo: func(repo, branch, goBranch string) bool {
if repo == "review" {
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// https://go.dev/issue/49529: git seems to be too slow on this
dashboard: skip x/review on slow 32-bit builders x/review is fairly disk-intensive (it shells out to 'git'), and also mostly for use by Go contributors (a smaller subset of Go users in general). It frequently times out on two particular 32-bit builders. I don't think we particularly need the coverage from those two builders for this repo, so rather than trying to speed up the test or tweak the scale factors, let's just skip it. Fixes golang/go#49529 Fixes golang/go#49530 Change-Id: I8da1216ebdf9287ae78d52bb03187b65eb33c9ee Reviewed-on: https://go-review.googlesource.com/c/build/+/363495 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-11 23:45:01 +03:00
// platform.
env,dashboard: add OpenBSD 7.0 all.bash takes a long time on these builders. I'll keep an eye on them to see if it causes trouble. For golang/go#48977. Change-Id: I0239a93c004157855968dab397e68abe38f5f439 Reviewed-on: https://go-review.googlesource.com/c/build/+/364094 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-15 23:02:19 +03:00
return false
}
return buildRepoByDefault(repo)
},
distTestAdjust: noTestDirAndNoReboot,
numTryTestHelpers: 4,
})
addBuilder(BuildConfig{
dashboard/builders: don't run mobile on Stretch builders, clean up I forgot to check buildRepoByDefault on the Stretch builders, so they started running x/mobile. Also noticed a ton of obsolete builders/checks, clean them out while I'm at it. In the tests, clear out very old version checks, and replace "arbitrary release branch" versions with go1.99 rather than whatever happened to be current when the test case was written. For golang/go#56414. Change-Id: I88eeeaec5d166d1ac1a3938dbc26870ff8d4b33a Reviewed-on: https://go-review.googlesource.com/c/build/+/446183 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-28 21:17:45 +03:00
Name: "openbsd-amd64-70",
HostType: "host-openbsd-amd64-70",
tryBot: defaultTrySet(),
distTestAdjust: noTestDirAndNoReboot,
env,dashboard: add OpenBSD 7.0 all.bash takes a long time on these builders. I'll keep an eye on them to see if it causes trouble. For golang/go#48977. Change-Id: I0239a93c004157855968dab397e68abe38f5f439 Reviewed-on: https://go-review.googlesource.com/c/build/+/364094 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-15 23:02:19 +03:00
numTryTestHelpers: 4,
})
addBuilder(BuildConfig{
Name: "openbsd-386-70",
HostType: "host-openbsd-386-70",
tryBot: explicitTrySet("sys"),
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard/builders: don't run mobile on Stretch builders, clean up I forgot to check buildRepoByDefault on the Stretch builders, so they started running x/mobile. Also noticed a ton of obsolete builders/checks, clean them out while I'm at it. In the tests, clear out very old version checks, and replace "arbitrary release branch" versions with go1.99 rather than whatever happened to be current when the test case was written. For golang/go#56414. Change-Id: I88eeeaec5d166d1ac1a3938dbc26870ff8d4b33a Reviewed-on: https://go-review.googlesource.com/c/build/+/446183 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-10-28 21:17:45 +03:00
// https://go.dev/issue/49529: git seems to be too slow on this
// platform.
return repo != "review" && buildRepoByDefault(repo)
dashboard: skip x/review on slow 32-bit builders x/review is fairly disk-intensive (it shells out to 'git'), and also mostly for use by Go contributors (a smaller subset of Go users in general). It frequently times out on two particular 32-bit builders. I don't think we particularly need the coverage from those two builders for this repo, so rather than trying to speed up the test or tweak the scale factors, let's just skip it. Fixes golang/go#49529 Fixes golang/go#49530 Change-Id: I8da1216ebdf9287ae78d52bb03187b65eb33c9ee Reviewed-on: https://go-review.googlesource.com/c/build/+/363495 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-11 23:45:01 +03:00
},
dashboard: promote OpenBSD 6.8 builders to be default The known issue with OpenBSD 6.8 builders appears to be resolved via CL 278732 and CL 279134. Promote them to the primary OpenBSD post-submit builders and TryBots. Having test coverage from OpenBSD 6.8 and 6.4 builders gives us us more confidence that Go works on supported OpenBSD versions (which are 6.8 and 6.7 at this time, per past policy decision in https://golang.org/issue/15227#issuecomment-293319876). Reduce numTryTestHelpers from 5 to 4 based on some data from golang.org/issue/37439 showing that going from 3 to 5 helpers doesn't make a significant difference. We can adjust further if we learn that OpenBSD TryBots become the bottleneck. Fixes golang/go#35712. For golang/go#42542. For golang/go#42064. Updates golang/go#42426. Change-Id: Id2fa4be7c3161f89752c1428146846fe06ca63db Reviewed-on: https://go-review.googlesource.com/c/build/+/279512 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org>
2020-12-21 22:12:25 +03:00
distTestAdjust: noTestDirAndNoReboot,
numTryTestHelpers: 4,
dashboard: add OpenBSD 6.8 builders This change builds on top of CL 268297, using the updated env script to build OpenBSD 6.8 images, and adding new builders that use them. This has been tested with cmd/debugnewvm on a recent Go tip commit, as well as Go 1.15.4 and 1.14.11 commits. It passed, although there were also some failures seen. Once the builder is added, we'll know the test results for a wider set of commits, and can decide how to proceed from there. Minimize the configuration to a bare minimum. Specifically, remove MinCPUPlatform since setting it "Intel Skylake" was found not to have a noticeable effect on the speed of the build compared to the zero value: # With MinCPUPlatform = "Intel Skylake": $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 17m8.308s # With a zero MinCPUPlatform value: $ time debugnewvm -run-build=openbsd-amd64-68 -rev=go1.15.4 [...] real 16m28.518s For golang/go#35712. Updates golang/go#42426. Change-Id: I517a85738a034a3a4074488ccecd4408a91a4a07 Reviewed-on: https://go-review.googlesource.com/c/build/+/269577 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-12 20:27:32 +03:00
})
dashboard: add n1 hosts for OpenBSD and NetBSD We recently migrated in CL 354757 from n1 to e2 hosts around the same time issues started appearing with these builders. n1 hosts are notably different in that they are older generation CPUs with hyperthreading disabled. For golang/go#49209 Change-Id: I8b6822fbd4910602f61d504b34580282c97c0ca7 Reviewed-on: https://go-review.googlesource.com/c/build/+/365776 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-19 22:22:11 +03:00
addBuilder(BuildConfig{
dashboard: clean up builders affected by memory corruption Remove freebsd 12.2, which is replaced by 12.3 with the XSAVE fix. Move freebsd 11.* to N2 machines, which are not affected. Remove openbsd and netbsd e2/n1/n2/n2d-specific configurations now that we have mostly understood the nature of that problem. Keep one around so that the runtime team can create gomotes. Move the "official" builder to the n2 cpu that works. For golang/go#49967, golang/go#49209, golang/go#40561. Fixes golang/go#50496. Change-Id: If6989317f06cbec95d5addb19d9e968aecfa3f8a Reviewed-on: https://go-review.googlesource.com/c/build/+/377474 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-10 23:09:53 +03:00
// This builder is only for the runtime team to use investigating golang/go#49209.
Name: "openbsd-386-70-n2d",
HostType: "host-openbsd-386-70-n2d",
buildsRepo: disabledBuilder,
dashboard: add n2 and n2d hosts for OpenBSD and NetBSD We recently migrated in CL 354757 from n1 to e2 hosts around the same time issues started appearing with these builders. n1 hosts are notably different in that they are older generation CPUs with hyperthreading disabled. e2 hosts may sometimes be AMD CPUs. n2d hosts are always AMD, so this helps bisect the problem. n2 hosts are always Intel. For golang/go#49209 Change-Id: I60334b44e192b0b95293891b380f2a89227b9235 Reviewed-on: https://go-review.googlesource.com/c/build/+/367534 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-29 19:15:30 +03:00
distTestAdjust: noTestDirAndNoReboot,
})
dashboard: add openbsd-arm-jsing builder This will allow the openbsd-arm builder to be migrated to a buildlet. Change-Id: If38788daf2d1e7f237ebdcce384a098e08bffb0b Reviewed-on: https://go-review.googlesource.com/c/build/+/192598 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-30 20:09:05 +03:00
addBuilder(BuildConfig{
dashboard: reduce the amount of work for openbsd/arm Given the performance of this hardware, reduce the amount of work that it is trying to do. Updates golang/go#25498 Change-Id: I943ab2b01bd10c5217c097464d3904b0f4de2d0a Reviewed-on: https://go-review.googlesource.com/c/build/+/228597 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-04-16 18:47:53 +03:00
Name: "openbsd-arm-jsing",
HostType: "host-openbsd-arm-joelsing",
SkipSnapshot: true,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: reduce the amount of work for openbsd/arm Given the performance of this hardware, reduce the amount of work that it is trying to do. Updates golang/go#25498 Change-Id: I943ab2b01bd10c5217c097464d3904b0f4de2d0a Reviewed-on: https://go-review.googlesource.com/c/build/+/228597 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-04-16 18:47:53 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
switch repo {
dashboard: add openbsd-arm64-jsing builder (reverse) Update golang/go#31656 Fixes golang/go#34035 Change-Id: I7e3d20be148ad5111efeb78702352da14274938e Reviewed-on: https://go-review.googlesource.com/c/build/+/250117 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-20 21:42:01 +03:00
case "go", "net", "sys":
return branch == "master" && goBranch == "master"
default:
return false
}
},
distTestAdjust: noTestDirAndNoReboot,
tryBot: nil,
env: []string{
// The machine is slow.
"GO_TEST_TIMEOUT_SCALE=5",
},
})
addBuilder(BuildConfig{
Name: "openbsd-arm64-jsing",
HostType: "host-openbsd-arm64-joelsing",
SkipSnapshot: true,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: add openbsd-arm64-jsing builder (reverse) Update golang/go#31656 Fixes golang/go#34035 Change-Id: I7e3d20be148ad5111efeb78702352da14274938e Reviewed-on: https://go-review.googlesource.com/c/build/+/250117 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-20 21:42:01 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
switch repo {
dashboard: add openbsd-mips64-jsing builder (reverse) Update golang/go#40995 Change-Id: Ie733438ab1823d65109e684a6a5e3098cdfdb252 Reviewed-on: https://go-review.googlesource.com/c/build/+/250118 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-23 19:02:40 +03:00
case "go", "net", "sys":
return branch == "master" && goBranch == "master"
default:
return false
}
},
distTestAdjust: noTestDirAndNoReboot,
tryBot: nil,
env: []string{
// The machine is slow.
"GO_TEST_TIMEOUT_SCALE=5",
},
})
addBuilder(BuildConfig{
Name: "openbsd-mips64-jsing",
HostType: "host-openbsd-mips64-joelsing",
SkipSnapshot: true,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: add openbsd-mips64-jsing builder (reverse) Update golang/go#40995 Change-Id: Ie733438ab1823d65109e684a6a5e3098cdfdb252 Reviewed-on: https://go-review.googlesource.com/c/build/+/250118 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-23 19:02:40 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
switch repo {
dashboard: reduce the amount of work for openbsd/arm Given the performance of this hardware, reduce the amount of work that it is trying to do. Updates golang/go#25498 Change-Id: I943ab2b01bd10c5217c097464d3904b0f4de2d0a Reviewed-on: https://go-review.googlesource.com/c/build/+/228597 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-04-16 18:47:53 +03:00
case "go", "net", "sys":
return branch == "master" && goBranch == "master"
default:
return false
}
},
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: noTestDirAndNoReboot,
tryBot: nil,
dashboard: add openbsd-arm-jsing builder This will allow the openbsd-arm builder to be migrated to a buildlet. Change-Id: If38788daf2d1e7f237ebdcce384a098e08bffb0b Reviewed-on: https://go-review.googlesource.com/c/build/+/192598 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-08-30 20:09:05 +03:00
env: []string{
// The machine is slow.
"GO_TEST_TIMEOUT_SCALE=5",
},
})
dashboard: add NetBSD 9.3 builders This adds the 9.3 builders created by running the make file and manually uploading and creating the VM images. Updates golang/go#54773 Change-Id: I0826b1fea1c486ec7cb34abad539672bddc39bb7 Reviewed-on: https://go-review.googlesource.com/c/build/+/450235 Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Joedian Reid <joedian@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-11-14 19:11:34 +03:00
addBuilder(BuildConfig{
Name: "netbsd-386-9_3",
HostType: "host-netbsd-386-9_3",
distTestAdjust: noTestDirAndNoReboot,
})
dashboard, env/netbsd-{amd64,386}: add NetBSD 9.0 builders Update NetBSD amd64 and 386 builders to the latest NetBSD 9.0 release, using the latest versions of anita (2.3) and pkgsrc packages (2019Q4). Also increase the image disk size from 4 GB to 16 GB. The motivation is to help tests that require more disk space and large dependencies. Additional adjustments to the image building script will need to be made to make use of increased disk space for the /tmp volume, as it is currently being mounted in RAM with size equal to 25% of memory. Remove the manual invocation of the mozilla-rootcerts install command. It no longer works as is in NetBSD 9.0. The mozilla-rootcerts-openssl package is added instead, which successfully performs that same task. Hopefully this will be a more robust approach for the future. Continue to use an explicit URL for the NetBSD release download, and remove unused find_latest_release. The plan is to roll out these builders first (without trybots), gain more confidence, enable trybots, and then remove NetBSD 8.0 builders. For golang/go#37244. For golang/go#30839. For golang/go#31858. For golang/go#31726. For golang/go#38283. Change-Id: Id41278eaebe64cfbcf7b1ab9bfd64e550ee0bbf1 Reviewed-on: https://go-review.googlesource.com/c/build/+/226977 Reviewed-by: Benny Siegert <bsiegert@gmail.com> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-02 15:55:30 +03:00
addBuilder(BuildConfig{
dashboard: add NetBSD 9.3 builders This adds the 9.3 builders created by running the make file and manually uploading and creating the VM images. Updates golang/go#54773 Change-Id: I0826b1fea1c486ec7cb34abad539672bddc39bb7 Reviewed-on: https://go-review.googlesource.com/c/build/+/450235 Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Joedian Reid <joedian@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-11-14 19:11:34 +03:00
Name: "netbsd-amd64-9_3",
HostType: "host-netbsd-amd64-9_3",
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: noTestDirAndNoReboot,
dashboard, cmd/racebuild: promote NetBSD 9.3 as the primary builder version This change removed the known issue from the NetBSD 9.3 builders. It also promotes 9.3 to be the primary version of NetBSD used in the build infrastructure. Updates golang/go#54773 Change-Id: If8b8aa89edb9ed8be564149ea728715b4a7b1085 Reviewed-on: https://go-review.googlesource.com/c/build/+/450715 Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org> Reviewed-by: Benny Siegert <bsiegert@gmail.com>
2022-11-15 19:17:14 +03:00
tryBot: explicitTrySet("sys"),
dashboard, env/netbsd-{amd64,386}: add NetBSD 9.0 builders Update NetBSD amd64 and 386 builders to the latest NetBSD 9.0 release, using the latest versions of anita (2.3) and pkgsrc packages (2019Q4). Also increase the image disk size from 4 GB to 16 GB. The motivation is to help tests that require more disk space and large dependencies. Additional adjustments to the image building script will need to be made to make use of increased disk space for the /tmp volume, as it is currently being mounted in RAM with size equal to 25% of memory. Remove the manual invocation of the mozilla-rootcerts install command. It no longer works as is in NetBSD 9.0. The mozilla-rootcerts-openssl package is added instead, which successfully performs that same task. Hopefully this will be a more robust approach for the future. Continue to use an explicit URL for the NetBSD release download, and remove unused find_latest_release. The plan is to roll out these builders first (without trybots), gain more confidence, enable trybots, and then remove NetBSD 8.0 builders. For golang/go#37244. For golang/go#30839. For golang/go#31858. For golang/go#31726. For golang/go#38283. Change-Id: Id41278eaebe64cfbcf7b1ab9bfd64e550ee0bbf1 Reviewed-on: https://go-review.googlesource.com/c/build/+/226977 Reviewed-by: Benny Siegert <bsiegert@gmail.com> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-02 15:55:30 +03:00
})
dashboard: add n2 and n2d hosts for OpenBSD and NetBSD We recently migrated in CL 354757 from n1 to e2 hosts around the same time issues started appearing with these builders. n1 hosts are notably different in that they are older generation CPUs with hyperthreading disabled. e2 hosts may sometimes be AMD CPUs. n2d hosts are always AMD, so this helps bisect the problem. n2 hosts are always Intel. For golang/go#49209 Change-Id: I60334b44e192b0b95293891b380f2a89227b9235 Reviewed-on: https://go-review.googlesource.com/c/build/+/367534 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-29 19:15:30 +03:00
addBuilder(BuildConfig{
dashboard: skip x/review on slow 32-bit builders x/review is fairly disk-intensive (it shells out to 'git'), and also mostly for use by Go contributors (a smaller subset of Go users in general). It frequently times out on two particular 32-bit builders. I don't think we particularly need the coverage from those two builders for this repo, so rather than trying to speed up the test or tweak the scale factors, let's just skip it. Fixes golang/go#49529 Fixes golang/go#49530 Change-Id: I8da1216ebdf9287ae78d52bb03187b65eb33c9ee Reviewed-on: https://go-review.googlesource.com/c/build/+/363495 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-11 23:45:01 +03:00
Name: "netbsd-arm-bsiegert",
HostType: "host-netbsd-arm-bsiegert",
buildsRepo: func(repo, branch, goBranch string) bool {
if repo == "review" {
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// https://go.dev/issue/49530: This test seems to be too slow even
dashboard: skip x/review on slow 32-bit builders x/review is fairly disk-intensive (it shells out to 'git'), and also mostly for use by Go contributors (a smaller subset of Go users in general). It frequently times out on two particular 32-bit builders. I don't think we particularly need the coverage from those two builders for this repo, so rather than trying to speed up the test or tweak the scale factors, let's just skip it. Fixes golang/go#49529 Fixes golang/go#49530 Change-Id: I8da1216ebdf9287ae78d52bb03187b65eb33c9ee Reviewed-on: https://go-review.googlesource.com/c/build/+/363495 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-11 23:45:01 +03:00
// with a long scale factor.
return false
}
return buildRepoByDefault(repo)
},
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: noTestDirAndNoReboot,
tryBot: nil,
dashboard: add netbsd-arm-bsiegert This seems to be the last builder still using the old builder binary and not buildlet. It needs an entry in here to switch to buildlet and stage0. Change-Id: If2fdd2298ab88d56b6850061050caf27ca7c8983 Reviewed-on: https://go-review.googlesource.com/c/build/+/168061 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-03-19 16:28:04 +03:00
env: []string{
// The machine is slow.
"GO_TEST_TIMEOUT_SCALE=10",
},
dashboard: remove NetBSD 9.0 builders The netbsd-386 and netbsd-amd64 builders with 9.3 contain various bugfixes, including to libpthread, that prevent test flakes. Remove the older version now. While here, remove issue golang/go#50138 (fixed) from the netbsd-arm* builders. Fixes golang/go#54773. Change-Id: Ibccf0817a69a3dd74651bd5a3f50ab77c3a92beb Reviewed-on: https://go-review.googlesource.com/c/build/+/454755 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com>
2022-12-02 17:06:40 +03:00
FlakyNet: true,
dashboard: add netbsd-arm-bsiegert This seems to be the last builder still using the old builder binary and not buildlet. It needs an entry in here to switch to buildlet and stage0. Change-Id: If2fdd2298ab88d56b6850061050caf27ca7c8983 Reviewed-on: https://go-review.googlesource.com/c/build/+/168061 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-03-19 16:28:04 +03:00
})
dashboard: add netbsd-arm64-bsiegert builder (reverse) Update golang/go#34036 Change-Id: Ic92093e764fa163d97a2f125a4534581adf217da Reviewed-on: https://go-review.googlesource.com/c/build/+/249137 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-08-18 21:42:30 +03:00
addBuilder(BuildConfig{
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
Name: "netbsd-arm64-bsiegert",
HostType: "host-netbsd-arm64-bsiegert",
dashboard: add netbsd-arm64-bsiegert builder (reverse) Update golang/go#34036 Change-Id: Ic92093e764fa163d97a2f125a4534581adf217da Reviewed-on: https://go-review.googlesource.com/c/build/+/249137 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-08-18 21:42:30 +03:00
distTestAdjust: noTestDirAndNoReboot,
tryBot: nil,
env: []string{
// The machine is slow.
"GO_TEST_TIMEOUT_SCALE=10",
},
dashboard: remove NetBSD 9.0 builders The netbsd-386 and netbsd-amd64 builders with 9.3 contain various bugfixes, including to libpthread, that prevent test flakes. Remove the older version now. While here, remove issue golang/go#50138 (fixed) from the netbsd-arm* builders. Fixes golang/go#54773. Change-Id: Ibccf0817a69a3dd74651bd5a3f50ab77c3a92beb Reviewed-on: https://go-review.googlesource.com/c/build/+/454755 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com>
2022-12-02 17:06:40 +03:00
FlakyNet: true,
dashboard: add netbsd-arm64-bsiegert builder (reverse) Update golang/go#34036 Change-Id: Ic92093e764fa163d97a2f125a4534581adf217da Reviewed-on: https://go-review.googlesource.com/c/build/+/249137 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2020-08-18 21:42:30 +03:00
})
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
addBuilder(BuildConfig{
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
Name: "plan9-386",
HostType: "host-plan9-386-gce",
dashboard: only test plan9 at master The plan9 port doesn't need to be tested against older Go releases. Its userbase runs at master. Change-Id: I710d98560b234c7555c7be526aa2efdb6473c439 Reviewed-on: https://go-review.googlesource.com/c/build/+/170519 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-03 08:03:37 +03:00
numTestHelpers: 1,
dashboard: disable plan9-386 builder It hasn't passed in months and now spins, wasting resources. Updates golang/go#31261 Updates golang/go#29801 Change-Id: Idcf13ae915bad4febb156c5c5d49f07f76cf9d49 Reviewed-on: https://go-review.googlesource.com/c/build/+/172797 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-04-18 22:33:19 +03:00
tryOnly: true, // disable it for now; Issue 31261, Issue 29801
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
distTestAdjust: func(run bool, distTest string, isNormalTry bool) bool {
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
switch distTest {
env/plan9: revert SMP changes, stop running cmd/go tests Revert "env: enable SMP in Plan 9 image" This reverts commit 6478d3e7bdff4c8d810ba44f970ca4b0bfc92405. Revert "dashboard: bump plan9 GCE image" This reverts commit ce208996bf954a87d68789bb6a9000256f016c77. Updates golang/go#29822 Change-Id: I47e75d135e092ee9d5a80c66e91c1048c67cd5f6 Reviewed-on: https://go-review.googlesource.com/c/158542 Reviewed-by: Bryan C. Mills <bcmills@google.com> Reviewed-by: David du Colombier <0intro@gmail.com>
2019-01-19 01:19:58 +03:00
case "api",
"go_test:cmd/go": // takes over 20 minutes without working SMP
return false
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
env/plan9: revert SMP changes, stop running cmd/go tests Revert "env: enable SMP in Plan 9 image" This reverts commit 6478d3e7bdff4c8d810ba44f970ca4b0bfc92405. Revert "dashboard: bump plan9 GCE image" This reverts commit ce208996bf954a87d68789bb6a9000256f016c77. Updates golang/go#29822 Change-Id: I47e75d135e092ee9d5a80c66e91c1048c67cd5f6 Reviewed-on: https://go-review.googlesource.com/c/158542 Reviewed-by: Bryan C. Mills <bcmills@google.com> Reviewed-by: David du Colombier <0intro@gmail.com>
2019-01-19 01:19:58 +03:00
},
dashboard: add known issues for plan9-386, plan9-386-0intro, and plan9-amd64-0intro For golang/go#52653. Updates golang/go#29801. Updates golang/go#49756. Updates golang/go#50137. Change-Id: Ided04da5c1e403c4a194c8c645c5179534a00907 Reviewed-on: https://go-review.googlesource.com/c/build/+/408698 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com>
2022-05-26 18:22:04 +03:00
buildsRepo: plan9Default,
KnownIssues: []int{29801},
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
})
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "windows-amd64-2008",
HostType: "host-windows-amd64-2008",
distTestAdjust: noTestDirAndNoReboot,
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return onlyGo(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
dashboard: increase TIMEOUT_SCALE to 2 for windows-amd64 cmd/go takes ~188 seconds on windows-amd64, which is over the default 180 second limit. Bump up the timout rate. Change-Id: Ib0e5289ab6c4d6127d18375e3a72453818b984a8 Reviewed-on: https://go-review.googlesource.com/110415 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-01 00:16:33 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-2008-oldcc",
HostType: "host-windows-amd64-2008-oldcc",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
distTestAdjust: noTestDirAndNoReboot,
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return onlyGo(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
})
cmd/buildlet, dashboard: support for v2 windows images, 386 builder - images now include 32bit gcc in c:\godeps\gcc32 - 64bit gcc has moved to c:\godeps\gcc64 - update host definitions for new image versions - add windows-386-2008 host Updates golang/go#17513 Change-Id: Ib3f5d4b2b1702c05089cf633529ebf38db270a43 Reviewed-on: https://go-review.googlesource.com/42014 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-27 23:12:08 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-386-2008",
HostType: "host-windows-amd64-2008",
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return defaultPlusExpBuild(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atLeastGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
dashboard: add windows-386-2012 builder This change adds a Windows 386 builder with version 2012 of Windows server. It replaces Windows 2008 as the version of Windows used for trybot runs. It also ensures Go 1.17 is the latest version of go being tested on Windows 2008 builders. Windows 2008 has reached its end of life and will be phased out. Updates golang/go#47845 Fixes golang/go#49490 Change-Id: I2307c68a74dfb41eb6a1a24177cc58835989d56b Reviewed-on: https://go-review.googlesource.com/c/build/+/363474 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-11-11 23:05:21 +03:00
numTryTestHelpers: 4,
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-386-2008-oldcc",
HostType: "host-windows-amd64-2008-oldcc",
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return defaultPlusExpBuild(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
distTestAdjust: fasterTrybots,
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atMostGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
numTryTestHelpers: 4,
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
})
dashboard: add windows-386-2012 builder This change adds a Windows 386 builder with version 2012 of Windows server. It replaces Windows 2008 as the version of Windows used for trybot runs. It also ensures Go 1.17 is the latest version of go being tested on Windows 2008 builders. Windows 2008 has reached its end of life and will be phased out. Updates golang/go#47845 Fixes golang/go#49490 Change-Id: I2307c68a74dfb41eb6a1a24177cc58835989d56b Reviewed-on: https://go-review.googlesource.com/c/build/+/363474 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-11-11 23:05:21 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-386-2012",
HostType: "host-windows-amd64-2012",
distTestAdjust: fasterTrybots,
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return onlyGo(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atLeastGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
numTryTestHelpers: 4,
cmd/buildlet, dashboard: support for v2 windows images, 386 builder - images now include 32bit gcc in c:\godeps\gcc32 - 64bit gcc has moved to c:\godeps\gcc64 - update host definitions for new image versions - add windows-386-2008 host Updates golang/go#17513 Change-Id: Ib3f5d4b2b1702c05089cf633529ebf38db270a43 Reviewed-on: https://go-review.googlesource.com/42014 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-27 23:12:08 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-386-2012-oldcc",
HostType: "host-windows-amd64-2012-oldcc",
distTestAdjust: fasterTrybots,
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return onlyGo(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
env: []string{"GOARCH=386", "GOHOSTARCH=386"},
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atMostGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
numTryTestHelpers: 4,
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
})
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-2012-oldcc",
HostType: "host-windows-amd64-2012-oldcc",
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: noTestDirAndNoReboot,
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return onlyGo(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
dashboard: increase TIMEOUT_SCALE to 2 for windows-amd64 cmd/go takes ~188 seconds on windows-amd64, which is over the default 180 second limit. Bump up the timout rate. Change-Id: Ib0e5289ab6c4d6127d18375e3a72453818b984a8 Reviewed-on: https://go-review.googlesource.com/110415 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-01 00:16:33 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
dashboard: add configs for new windows 2008, 2012, 2016 builders See also: https://golang.org/cl/41142 Updates golang/go#17513 Change-Id: Ie743ae4604e65892e28423ed0af008450b647197 Reviewed-on: https://go-review.googlesource.com/41393 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2017-04-21 22:35:28 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-2012",
HostType: "host-windows-amd64-2012",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
distTestAdjust: noTestDirAndNoReboot,
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return onlyGo(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
})
build: use buildlet on Windows Also adds "gomote rmall" command. Fixes golang/go#8640 Fixes golang/go#9799 Change-Id: I41b62b16df5e855e1367a9cc1c370bb1f928c242 Reviewed-on: https://go-review.googlesource.com/4132 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2015-02-07 04:32:15 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-2016",
HostType: "host-windows-amd64-2016",
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return defaultPlusExpBuild(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
distTestAdjust: fasterTrybots,
dashboard: increase TIMEOUT_SCALE to 2 for windows-amd64 cmd/go takes ~188 seconds on windows-amd64, which is over the default 180 second limit. Bump up the timout rate. Change-Id: Ib0e5289ab6c4d6127d18375e3a72453818b984a8 Reviewed-on: https://go-review.googlesource.com/110415 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-01 00:16:33 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atLeastGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atLeastGo1(goBranch, 20)
},
dashboard: update Windows builders, remove old manual Windows builder And clean up some other builders. Change-Id: I1f71836da7008e58d3e76e2cc3170e96cd57ddf6 Reviewed-on: https://go-review.googlesource.com/51432 Reviewed-by: Jeff Johnson <jrjohnson@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-27 07:52:12 +03:00
numTryTestHelpers: 5,
build: use buildlet on Windows Also adds "gomote rmall" command. Fixes golang/go#8640 Fixes golang/go#9799 Change-Id: I41b62b16df5e855e1367a9cc1c370bb1f928c242 Reviewed-on: https://go-review.googlesource.com/4132 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2015-02-07 04:32:15 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-2016-oldcc",
HostType: "host-windows-amd64-2016-oldcc",
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return defaultPlusExpBuild(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
distTestAdjust: fasterTrybots,
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2",
},
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
tryBot: func(repo, branch, goBranch string) bool {
// See comment above about the atMostGo1 call below.
dft := defaultTrySet()
return dft(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
},
numTryTestHelpers: 5,
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
})
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-longtest-oldcc",
HostType: "host-windows-amd64-2016-big-oldcc",
cmd/coordinator: delete useScheduler knob & old pre-scheduler hacks, code, TODOs Updates golang/go#19178 Change-Id: Id4d8b016c41f57bfaba5ee4ab046285607047493 Reviewed-on: https://go-review.googlesource.com/c/build/+/207178 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-11-14 18:43:33 +03:00
Notes: "Windows Server 2016 with go test -short=false",
dashboard: include longtest builders for trybots on release branches The goal of this test policy change is to decrease the chance of a Go repository release branch from getting into a state where some longtest post-submit builders are failing, as this will interfere with the ability to issue releases after golang/go#29252 is fixed. There are not that many CLs sent to release branches, so the extra latency caused by slower longtest builders being a part of trybots should not be very disruptive. For golang/go#37827. For golang/go#29252. Change-Id: I819b120bb7b763df4acf4583375cdb840793d323 Reviewed-on: https://go-review.googlesource.com/c/build/+/235338 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-05-27 01:19:05 +03:00
tryBot: func(repo, branch, goBranch string) bool {
onReleaseBranch := strings.HasPrefix(branch, "release-branch.")
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return atMostGo1(goBranch, 19) &&
repo == "go" && onReleaseBranch // See issue 37827.
dashboard: include longtest builders for trybots on release branches The goal of this test policy change is to decrease the chance of a Go repository release branch from getting into a state where some longtest post-submit builders are failing, as this will interfere with the ability to issue releases after golang/go#29252 is fixed. There are not that many CLs sent to release branches, so the extra latency caused by slower longtest builders being a part of trybots should not be very disruptive. For golang/go#37827. For golang/go#29252. Change-Id: I819b120bb7b763df4acf4583375cdb840793d323 Reviewed-on: https://go-review.googlesource.com/c/build/+/235338 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-05-27 01:19:05 +03:00
},
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
// See comment above about the atMostGo1 call below.
b := defaultPlusExpBuild(repo, branch, goBranch) &&
atMostGo1(goBranch, 19)
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
dashboard: adjust the windows-amd64-longtest policy It shouldn't build more repos than windows-amd64-2016. Fixes golang/go#35185 Change-Id: I310e2ccc521d88692fcf904fe53b4bae94f3f0f0 Reviewed-on: https://go-review.googlesource.com/c/build/+/203885 Reviewed-by: Bryan C. Mills <bcmills@google.com> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-28 23:16:36 +03:00
}
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
return b
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
},
needsGoProxy: true, // for cmd/go module tests
env: []string{
"GO_TEST_TIMEOUT_SCALE=5", // give them lots of time
},
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/42661.
dashboard: add windows and 32-bit longtest builders Fixes golang/go#29641 Fixes golang/go#26529 Change-Id: I5ab3aa443276ab36b866d7fabc1d78a82b34cb64 Reviewed-on: https://go-review.googlesource.com/c/build/+/202479 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-21 19:58:47 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-longtest",
HostType: "host-windows-amd64-2016-big",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
Notes: "Windows Server 2016 with go test -short=false",
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
tryBot: func(repo, branch, goBranch string) bool {
onReleaseBranch := strings.HasPrefix(branch, "release-branch.")
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return atLeastGo1(goBranch, 20) &&
repo == "go" && onReleaseBranch // See issue 37827.
},
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
// See comment above about the atMostGo1 call below.
b := atLeastGo1(goBranch, 20) &&
defaultPlusExpBuild(repo, branch, goBranch)
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
}
return b
},
needsGoProxy: true, // for cmd/go module tests
env: []string{
"GO_TEST_TIMEOUT_SCALE=5", // give them lots of time
},
dashboard: shard linux-amd64-longtest-race and windows-amd64-longtest-newcc builders Fixes golang/go#56907. Change-Id: Iede30e41588326d6922f95c7c2dc1e837d801cfc Reviewed-on: https://go-review.googlesource.com/c/build/+/452857 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 00:02:00 +03:00
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/42661.
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
})
build: use buildlet on Windows Also adds "gomote rmall" command. Fixes golang/go#8640 Fixes golang/go#9799 Change-Id: I41b62b16df5e855e1367a9cc1c370bb1f928c242 Reviewed-on: https://go-review.googlesource.com/4132 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2015-02-07 04:32:15 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-oldcc-race",
HostType: "host-windows-amd64-2016-oldcc",
dashboard, cmd/coordinator: various fixes * add support for longtest builders for subrepos. * fix race builders for subrepos (they weren't passing the -race flag). * adjust the policy for the js-wasm builders to build fewer subrepos where it'll never work or isn't worth it. * fix the android emu builders which disappeared because an empty string was being passed to buildsRepoAtAll. In some places in the code an empty string for goBranch for the "go" repo meant the same as branch, but I forgot that in the new code, so an old caller was confusing the new config hooks. Rather than make all policy funcs be aware of both ways, the new code in this CL now maps an empty string to the same as the repo's branch when the repo == "go". Adds a test too. * fix some outdated comments. Change-Id: Icf3fb85e5542a4d314443b59d02517b306ef46b7 Reviewed-on: https://go-review.googlesource.com/c/build/+/166897 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-11 21:49:56 +03:00
Notes: "Only runs -race tests (./race.bat)",
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has legacy C compilers installed, suitable
// for versions of Go prior to 1.20, hence the atMostGo1
// call below. Newer (1.20 and later) will use the
// non-oldcc variant instead. See issue 35006 for more
// details.
return atMostGo1(goBranch, 19) &&
buildRepoByDefault(repo)
},
dashboard: increase TIMEOUT_SCALE to 2 for windows-amd64 cmd/go takes ~188 seconds on windows-amd64, which is over the default 180 second limit. Bump up the timout rate. Change-Id: Ib0e5289ab6c4d6127d18375e3a72453818b984a8 Reviewed-on: https://go-review.googlesource.com/110415 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-01 00:16:33 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2"},
build: use buildlet on Windows Also adds "gomote rmall" command. Fixes golang/go#8640 Fixes golang/go#9799 Change-Id: I41b62b16df5e855e1367a9cc1c370bb1f928c242 Reviewed-on: https://go-review.googlesource.com/4132 Reviewed-by: Andrew Gerrand <adg@golang.org> Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2015-02-07 04:32:15 +03:00
})
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
addBuilder(BuildConfig{
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
Name: "windows-amd64-race",
HostType: "host-windows-amd64-2016",
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
Notes: "Only runs -race tests (./race.bat)",
dashboard: default to new compilers for windows amd64/386 builders Revamp the setup for windows-amd64 and windows-386 builders so that we default to using newer C compilers for Go 1.20 and main branch, but older compilers for release branches (1.19 and prior). Instead of having a series of "newcc" canary builders for windows, we now have a series of "oldcc" builders for release branch use. Note for posterity: we can prune these changes out in a couple of Go release (once Go 1.20 becomes the oldest release we're testing). Updates golang/go#35006. Change-Id: I329b59a5d67c2c1ae65a30564a1c6a081b2523fa Reviewed-on: https://go-review.googlesource.com/c/build/+/453095 Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Than McIntosh <thanm@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-23 17:32:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This builder has modern/recent C compilers installed,
// meaning that we only want to use it with 1.20+ versions
// of Go, hence the atLeastGo1 call below; versions of Go
// prior to 1.20 will use the *-oldcc variant instead. See
// issue 35006 for more details.
return atLeastGo1(goBranch, 20) &&
buildRepoByDefault(repo)
},
dashboard: add "*-newcc" windows builders with updated VMs Add a set of new "*-newcc" windows 386/amd64 builders that use new Windows VMs that incorporate updated GCP base images and updated C compilers. These builders are tagged with a known issue (35006) and are not included in any trybot sets at the moment. This change is intended to make it easier to work on the remaining issues blocking the adoption of the new compilers; once we have fixes checked in we can get rid of these builders and roll the default windows builders to the "*v8" images. Updates golang/go#35006. Change-Id: I1a7fb5699c20428a846b932e395aeb10ad7adfa9 Reviewed-on: https://go-review.googlesource.com/c/build/+/413415 Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Than McIntosh <thanm@google.com>
2022-06-21 17:27:54 +03:00
env: []string{
"GOARCH=amd64",
"GOHOSTARCH=amd64",
// cmd/go takes ~188 seconds on windows-amd64
// now, which is over the 180 second default
// dist test timeout. So, bump this builder
// up:
"GO_TEST_TIMEOUT_SCALE=2"},
})
dashboard: add new Windows ARM builder This partially reverts CL 229559, while adjusting it to use a new builder. The builder will be used now for windows/arm and later for windows/arm64. Updates golang/go#42604. Updates golang/go#38607. Updates golang/go#36439. Change-Id: I1ab661a6585e64de8196955c077715b32dc732b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/272106 Run-TryBot: Jason A. Donenfeld <Jason@zx2c4.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Alex Brainman <alex.brainman@gmail.com> Trust: Jason A. Donenfeld <Jason@zx2c4.com>
2020-11-20 20:35:33 +03:00
addBuilder(BuildConfig{
dashboard: remove issue for windows/arm builder We originally left the issue attached to the builder, before we knew that it worked. But it appears to be working well, with no shortage of work to do from farmer. Fixes golang/go#38607. Change-Id: I0e654c825a92b64132efbc409b768e5e83967802 Reviewed-on: https://go-review.googlesource.com/c/build/+/273786 Trust: Jason A. Donenfeld <Jason@zx2c4.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-11-28 17:02:05 +03:00
Name: "windows-arm-zx2c4",
HostType: "host-windows-arm64-zx2c4",
dashboard: add new Windows ARM builder This partially reverts CL 229559, while adjusting it to use a new builder. The builder will be used now for windows/arm and later for windows/arm64. Updates golang/go#42604. Updates golang/go#38607. Updates golang/go#36439. Change-Id: I1ab661a6585e64de8196955c077715b32dc732b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/272106 Run-TryBot: Jason A. Donenfeld <Jason@zx2c4.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Alex Brainman <alex.brainman@gmail.com> Trust: Jason A. Donenfeld <Jason@zx2c4.com>
2020-11-20 20:35:33 +03:00
env: []string{
"GOARM=7",
dashboard: expand time scale for windows-arm builder This builder has very slow I/O and could benefit from some extra time on a few tests. At the moment, the tests for x/review/git-codereview are failing with a time out, for example. Updates golang/go#42925. Change-Id: I532f4ddd3b9e7fd0a66ea9631b3fa7ce363e05a4 Reviewed-on: https://go-review.googlesource.com/c/build/+/274572 Trust: Jason A. Donenfeld <Jason@zx2c4.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-12-01 22:06:23 +03:00
"GO_TEST_TIMEOUT_SCALE=3"},
dashboard: add new Windows ARM builder This partially reverts CL 229559, while adjusting it to use a new builder. The builder will be used now for windows/arm and later for windows/arm64. Updates golang/go#42604. Updates golang/go#38607. Updates golang/go#36439. Change-Id: I1ab661a6585e64de8196955c077715b32dc732b8 Reviewed-on: https://go-review.googlesource.com/c/build/+/272106 Run-TryBot: Jason A. Donenfeld <Jason@zx2c4.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Alex Brainman <alex.brainman@gmail.com> Trust: Jason A. Donenfeld <Jason@zx2c4.com>
2020-11-20 20:35:33 +03:00
})
dashboard: add windows-arm64-10 reverse buildlet This adds a reverse buildlet for Windows ARM64 running under qemu on M1 Mac Minis. The VM currently boots, but more changes are needed to stage0 and buildlet in order for the builder to run. For golang/go#42604. Change-Id: Ie86e596c0f166d2ca8c075c0c971fcd1e34e940f Reviewed-on: https://go-review.googlesource.com/c/build/+/328311 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-15 23:42:51 +03:00
addBuilder(BuildConfig{
Name: "windows-arm64-10",
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
HostType: "host-windows-arm64-mini",
dashboard: add windows-arm64-10 reverse buildlet This adds a reverse buildlet for Windows ARM64 running under qemu on M1 Mac Minis. The VM currently boots, but more changes are needed to stage0 and buildlet in order for the builder to run. For golang/go#42604. Change-Id: Ie86e596c0f166d2ca8c075c0c971fcd1e34e940f Reviewed-on: https://go-review.googlesource.com/c/build/+/328311 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-06-15 23:42:51 +03:00
numTryTestHelpers: 1,
dashboard: add windows-arm-10 builder This adds a windows-arm builder using host-windows-arm64-mini hosts. The new BuildConfig has a KnownIssue until we can verify that the builders are building correctly. For golang/go#47019 Change-Id: I0505d4dc367dbb687290facbddc718eb13567025 Reviewed-on: https://go-review.googlesource.com/c/build/+/344990 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-08-25 22:50:51 +03:00
env: []string{
"GOARCH=arm64",
},
})
all: add Windows 11 builder Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-12 01:15:28 +03:00
addBuilder(BuildConfig{
Name: "windows-arm64-11",
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
HostType: "host-windows11-arm64-mini",
all: add Windows 11 builder Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-12 01:15:28 +03:00
numTryTestHelpers: 1,
env: []string{
"GOARCH=arm64",
dashboard: reduce GOMAXPROCS on Windows 11 ARM64 The Windows 11 ARM64 builder is experiencing occasional OOMs while building tests. Reducing GOMAXPROCS will reduce the go command's parallelism and hopefully prevent them. For golang/go#51019. Change-Id: Ia4bfdddaca178c130b9b57087a66a54cff903a05 Reviewed-on: https://go-review.googlesource.com/c/build/+/385182 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-02-11 21:34:27 +03:00
"GOMAXPROCS=4", // OOM problems, see go.dev/issue/51019
all: add Windows 11 builder Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-12 01:15:28 +03:00
},
dashboard: add known issue for windows-arm64-11 For golang/go#52653. Updates golang/go#51019. Change-Id: Ie57f7b2c2b6d4c3cc4b5f5f886773dff2a36a61e Reviewed-on: https://go-review.googlesource.com/c/build/+/408702 TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-05-26 18:39:11 +03:00
KnownIssues: []int{51019},
all: add Windows 11 builder Add a new host type, host-windows11-arm64-mini. It should support both ARM64 and ARM builds but for starters let's focus on ARM64. For golang/go#48946, golang/go#47019. Change-Id: I7ff07a97661fb6621237b9801ff0d0e338c6d4f4 Reviewed-on: https://go-review.googlesource.com/c/build/+/377696 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-01-12 01:15:28 +03:00
})
all: add a macOS 10.14 (Mojave) builder Fixes golang/go#27806 Change-Id: I576f563acb2c50cd0456cd4e6a1271b9aa59c9df Reviewed-on: https://go-review.googlesource.com/c/build/+/169498 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-27 02:04:31 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "darwin-amd64-10_14",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
HostType: "host-darwin-amd64-10_14-aws",
distTestAdjust: macTestPolicy,
dashboard,internal/releasetargets: run AMD64 Macs AWS, build 1.20 with 13 The AWS builders have been up and running reliably for a while now. Switch over. Unfortunately the macOS 13 builder had -aws in its name, so we're creating a new builder and will need a backfill. So it goes. While I'm here, build 1.20 with 13 now that we have it. For golang/go#48945, golang/go#40561. Change-Id: Idaac9cfea6fe3f5e190432ecb512a453812618c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/453956 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-11-29 21:41:35 +03:00
buildsRepo: defaultPlusExp,
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
})
dashboard, cmd/makemac: add macOS 10.15 Catalina builder Added the macOS 10.15 Catalina builder to the dashboard. Catalina builders should use the Mojave guestid in vSphere 6.7 update 3 because the Catalina guestid is not available in this version of vSphere. A Catalina builder will run on this version of vSphere with the Mojave guestid. Modified the expected number of vm instances running on Macstadium due to the addition of macOS 10.15 builders. Updates golang/go#34748 Change-Id: If14f6e088afc05dd1783460f21907e9345e3c338 Reviewed-on: https://go-review.googlesource.com/c/build/+/207937 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-11-19 17:55:01 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "darwin-amd64-10_15",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
HostType: "host-darwin-amd64-10_15-aws",
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
})
dashboard: add macOS 11.0 Big Sur builder This change adds macOS 11.0 Big Sur builder to the dashboard. It will not spawn an instance on the older MacStadium cluster which we are migrating away from. It will be marked with a known issue until until we have migrated away from the old cluster and makemac has been updated to process the new macOS versioning convention. Updates golang/go#40762 Updates golang/go#40757 Updates golang/go#40761 Change-Id: I24ce615a2c0c55dd75beed4f821119d4058ad8af Reviewed-on: https://go-review.googlesource.com/c/build/+/288192 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-01-29 23:47:13 +03:00
addBuilder(BuildConfig{
Name: "darwin-amd64-11_0",
dashboard,internal/releasetargets: run AMD64 Macs AWS, build 1.20 with 13 The AWS builders have been up and running reliably for a while now. Switch over. Unfortunately the macOS 13 builder had -aws in its name, so we're creating a new builder and will need a backfill. So it goes. While I'm here, build 1.20 with 13 now that we have it. For golang/go#48945, golang/go#40561. Change-Id: Idaac9cfea6fe3f5e190432ecb512a453812618c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/453956 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-11-29 21:41:35 +03:00
HostType: "host-darwin-amd64-11-aws",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
})
dashboard: add darwin-amd64-nocgo config, remove nacl-386 trybot Also remove dead nacl-arm. It hasn't run in ages. And update netbsd comment about why 386 doesn't run. And correct its VM image name. Updates golang/go#31705 Updates golang/go#31726 Change-Id: I9de4605f34a052d0a84684fca098388d75602a82 Reviewed-on: https://go-review.googlesource.com/c/build/+/174637 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 01:37:31 +03:00
addBuilder(BuildConfig{
all: add macOS 12 AMD64 builders I'm not 100% sure they'll work, so just one for now. I've updated the documentation according to my very shaky understanding. For golang/go#49149. Change-Id: Ic8f3b7fe96a1a6c18c0940a4aa2d08ec9dc2138b Reviewed-on: https://go-review.googlesource.com/c/build/+/365194 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-17 01:09:45 +03:00
Name: "darwin-amd64-12_0",
dashboard,internal/releasetargets: run AMD64 Macs AWS, build 1.20 with 13 The AWS builders have been up and running reliably for a while now. Switch over. Unfortunately the macOS 13 builder had -aws in its name, so we're creating a new builder and will need a backfill. So it goes. While I'm here, build 1.20 with 13 now that we have it. For golang/go#48945, golang/go#40561. Change-Id: Idaac9cfea6fe3f5e190432ecb512a453812618c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/453956 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-11-29 21:41:35 +03:00
HostType: "host-darwin-amd64-12-aws",
all: add macOS 12 AMD64 builders I'm not 100% sure they'll work, so just one for now. I've updated the documentation according to my very shaky understanding. For golang/go#49149. Change-Id: Ic8f3b7fe96a1a6c18c0940a4aa2d08ec9dc2138b Reviewed-on: https://go-review.googlesource.com/c/build/+/365194 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-17 01:09:45 +03:00
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
})
dashboard: add darwin 13 (Ventura) amd64 builders on AWS For golang/go#48945. For golang/go#55355. Change-Id: Ic8f346995024c69a3a8f2b91681e4ff90280f2c6 Reviewed-on: https://go-review.googlesource.com/c/build/+/448435 Auto-Submit: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-07 21:19:29 +03:00
addBuilder(BuildConfig{
dashboard,internal/releasetargets: run AMD64 Macs AWS, build 1.20 with 13 The AWS builders have been up and running reliably for a while now. Switch over. Unfortunately the macOS 13 builder had -aws in its name, so we're creating a new builder and will need a backfill. So it goes. While I'm here, build 1.20 with 13 now that we have it. For golang/go#48945, golang/go#40561. Change-Id: Idaac9cfea6fe3f5e190432ecb512a453812618c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/453956 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-11-29 21:41:35 +03:00
Name: "darwin-amd64-13",
dashboard: add darwin 13 (Ventura) amd64 builders on AWS For golang/go#48945. For golang/go#55355. Change-Id: Ic8f346995024c69a3a8f2b91681e4ff90280f2c6 Reviewed-on: https://go-review.googlesource.com/c/build/+/448435 Auto-Submit: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-07 21:19:29 +03:00
HostType: "host-darwin-amd64-13-aws",
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
})
all: add macOS 12 AMD64 builders I'm not 100% sure they'll work, so just one for now. I've updated the documentation according to my very shaky understanding. For golang/go#49149. Change-Id: Ic8f3b7fe96a1a6c18c0940a4aa2d08ec9dc2138b Reviewed-on: https://go-review.googlesource.com/c/build/+/365194 Trust: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-17 01:09:45 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "darwin-amd64-nocgo",
dashboard: add darwin-amd64 AWS reverse builder Used for AWS Mac prototyping. For #48945. Change-Id: Icd0d72ca1ad1b8d4dc6d843c4899d2207d8c6f9e Reviewed-on: https://go-review.googlesource.com/c/build/+/430696 Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-09-13 23:03:19 +03:00
HostType: "host-darwin-amd64-12-aws",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
distTestAdjust: noTestDirAndNoReboot,
env: []string{"CGO_ENABLED=0"},
dashboard: add darwin-amd64 AWS reverse builder Used for AWS Mac prototyping. For #48945. Change-Id: Icd0d72ca1ad1b8d4dc6d843c4899d2207d8c6f9e Reviewed-on: https://go-review.googlesource.com/c/build/+/430696 Reviewed-by: Jenny Rakoczy <jenny@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-09-13 23:03:19 +03:00
})
all: turn up new Mac Minis as their own host type The new minis are the official darwin arm64 builders. Split them out into a new host type, add monitoring, and remove existing deps on the toothrot builders. We honor them for their service. Fixes golang/go#49149. Change-Id: I8e4e6aa336e2acbd6812e25aa6a929aaa50a12f8 Reviewed-on: https://go-review.googlesource.com/c/build/+/406021 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-05-13 22:12:21 +03:00
addBuilder(BuildConfig{
Name: "darwin-arm64-11",
HostType: "host-darwin-arm64-11",
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
})
addBuilder(BuildConfig{
Name: "darwin-arm64-12",
HostType: "host-darwin-arm64-12",
dashboard: add darwin-arm64-12_0 builder Upgrades our arm64-11_0 builder. For golang/go#49149 Change-Id: I517cc5a999cea0cbc96ee2a6d3901840e2473b6a Reviewed-on: https://go-review.googlesource.com/c/build/+/365736 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-18 19:31:07 +03:00
distTestAdjust: macTestPolicy,
buildsRepo: defaultPlusExpBuild,
dashboard: add new darwin-arm64-11_0-toothrot builder These builders are run by the Go team. They are non-hermetic. For golang/go#39782 Change-Id: Ie402faf9a92ff6c667c8da6fc0dac8528331df48 Reviewed-on: https://go-review.googlesource.com/c/build/+/278432 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-12-15 20:58:50 +03:00
})
build: add macoS Sierra builder Change-Id: I10a7a9e44a158fdce5287a9b0b065b35d11fb502 Reviewed-on: https://go-review.googlesource.com/35470 Reviewed-by: Chris Broadfoot <cbro@golang.org>
2017-01-19 01:45:12 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "darwin-amd64-race",
dashboard: add all AWS darwin-amd64 builders All of the existing darwin-amd64 builders get AWS equivalents. For golang/go#48945. Change-Id: I076c19a47b6cc1fa1fb1be25219e6616497e1dc9 Reviewed-on: https://go-review.googlesource.com/c/build/+/432857 Run-TryBot: Michael Pratt <mpratt@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-09-22 20:01:05 +03:00
HostType: "host-darwin-amd64-12-aws",
distTestAdjust: macTestPolicy,
buildsRepo: onlyGo,
})
dashboard: add Zenly's virtual iOS builders Fixes golang/go#31722 Change-Id: Ia7f0d3f2e1a25000c42a10ff58d7e91d384b1219 Reviewed-on: https://go-review.googlesource.com/c/build/+/174797 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 21:33:26 +03:00
addBuilder(BuildConfig{
dashboard,env: move iOS builders to GOOS=ios Updates golang/go#41610 Change-Id: Ie8cb3294da5566e09fc06c01e679b8b773a439cf Reviewed-on: https://go-review.googlesource.com/c/build/+/259358 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Elias Naur <mail@eliasnaur.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-10-03 12:37:07 +03:00
Name: "ios-arm64-corellium",
HostType: "host-ios-arm64-corellium-ios",
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Notes: "Virtual iPhone SE running on Corellium; owned by zenly (github.com/znly)",
dashboard: add Zenly's virtual iOS builders Fixes golang/go#31722 Change-Id: Ia7f0d3f2e1a25000c42a10ff58d7e91d384b1219 Reviewed-on: https://go-review.googlesource.com/c/build/+/174797 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 21:33:26 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: add Zenly's virtual Android builders Change-Id: Id0be99f343a819c19b0004dc4160175c9bb0ace9 Reviewed-on: https://go-review.googlesource.com/c/build/+/174798 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 23:28:43 +03:00
return repo == "go" && branch == "master" && goBranch == "master"
},
})
addBuilder(BuildConfig{
Name: "android-arm64-corellium",
HostType: "host-android-arm64-corellium-android",
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Notes: "Virtual Android running on Corellium; owned by zenly (github.com/znly)",
dashboard: add Zenly's virtual Android builders Change-Id: Id0be99f343a819c19b0004dc4160175c9bb0ace9 Reviewed-on: https://go-review.googlesource.com/c/build/+/174798 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 23:28:43 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: add Zenly's virtual iOS builders Fixes golang/go#31722 Change-Id: Ia7f0d3f2e1a25000c42a10ff58d7e91d384b1219 Reviewed-on: https://go-review.googlesource.com/c/build/+/174797 Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-01 21:33:26 +03:00
return repo == "go" && branch == "master" && goBranch == "master"
},
})
dashboard: add android/arm builder on Corellium Updates golang/go#31722 Change-Id: I07d9f85d47b6cda5eadcfc4f93adff42316f0ff5 Reviewed-on: https://go-review.googlesource.com/c/build/+/174857 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-02 01:54:54 +03:00
addBuilder(BuildConfig{
Name: "android-arm-corellium",
HostType: "host-android-arm64-corellium-android",
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
Notes: "Virtual Android running on Corellium; owned by zenly (github.com/znly)",
dashboard: add android/arm builder on Corellium Updates golang/go#31722 Change-Id: I07d9f85d47b6cda5eadcfc4f93adff42316f0ff5 Reviewed-on: https://go-review.googlesource.com/c/build/+/174857 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-02 01:54:54 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return repo == "go" && branch == "master" && goBranch == "master"
},
env: []string{
"CGO_ENABLED=1",
"GOARCH=arm",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=2", // inherited from cmd/dist's default for GOARCH=arm
dashboard: add android/arm builder on Corellium Updates golang/go#31722 Change-Id: I07d9f85d47b6cda5eadcfc4f93adff42316f0ff5 Reviewed-on: https://go-review.googlesource.com/c/build/+/174857 TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-02 01:54:54 +03:00
},
})
env/android-amd64-emu: add new Android emulator container + VM image Now that we can do nested virtualization on GCE, that means we can run the Android emulator (which requires KVM) on GCE and at least get fast trybots and such for android-amd64. Updates golang/go#23824 Change-Id: I0da38c7fa0f15492230a31291d2921ba72f2151d Reviewed-on: https://go-review.googlesource.com/c/163738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:35:29 +03:00
addBuilder(BuildConfig{
Name: "android-386-emu",
dashboard: rename host-android-amd64-emu to host-linux-amd64-androidemu This follows the name convention and avoids a HostArch line. For golang/go#44505. Change-Id: I14654e64751ee830101e1191bd44cd426b3ecce2 Reviewed-on: https://go-review.googlesource.com/c/build/+/420804 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-08-03 22:43:12 +03:00
HostType: "host-linux-amd64-androidemu", // same amd64 host is used for 386 builder
dashboard: configure android-amd64-emu as post-submit only It has been decided in go.dev/issue/53377 for this builder to start being post-submit only. Update the builder configuration accordingly. Keep it as a TryBot only in x/mobile, where its signal should still be a net positive contribution despite the noise in its results. Fixes golang/go#53377. Change-Id: I44ee5454bfe2de15e2f41a82900ee2acc37cd211 Reviewed-on: https://go-review.googlesource.com/c/build/+/407615 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-05-21 00:26:59 +03:00
Notes: "Android emulator on GCE (GOOS=android GOARCH=386)",
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b := buildRepoByDefault(repo)
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
switch repo {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
case "mobile":
b = true
dashboard: stop testing x/build on even more builders Follow up to CL 210378 after looking at: https://build.golang.org/?repo=golang.org%2fx%2fbuild Updates golang/go#30640 Change-Id: I81505a9ca2985ffa6e75922665b14ef4de2af860 Reviewed-on: https://go-review.googlesource.com/c/build/+/211100 Reviewed-by: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-12-12 20:43:59 +03:00
case "build", "blog", "talks", "review", "tour", "website":
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b = false
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
}
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
return b
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
},
env/android-amd64-emu: add new Android emulator container + VM image Now that we can do nested virtualization on GCE, that means we can run the Android emulator (which requires KVM) on GCE and at least get fast trybots and such for android-amd64. Updates golang/go#23824 Change-Id: I0da38c7fa0f15492230a31291d2921ba72f2151d Reviewed-on: https://go-review.googlesource.com/c/163738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:35:29 +03:00
env: []string{
"GOARCH=386",
"GOOS=android",
"GOHOSTARCH=amd64",
"GOHOSTOS=linux",
"CGO_ENABLED=1",
},
dashboard: add known issues for android-*-emu Issue golang/go#42212 manifests as test timeouts, and is by far the most frequent of these known issues. Issue golang/go#51001 causes failures with "systemstack called from unexpected goroutine". It seems to have been introduced sometime last year, but it isn't clear to me whether it is a regression or an older (latent) bug unearthed by some other change. Issue golang/go#52724 appears to be a bug or race in the Android emulator itself. It might require a builder image update and/or escalation to the maintainers of the emulator proper. Updates golang/go#53377. Change-Id: I677915b1ff02dd02e0f14c63b0d25caf11e27a72 Reviewed-on: https://go-review.googlesource.com/c/build/+/412174 Reviewed-by: David Chase <drchase@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com>
2022-06-14 22:17:34 +03:00
KnownIssues: []int{42212, 51001, 52724},
env/android-amd64-emu: add new Android emulator container + VM image Now that we can do nested virtualization on GCE, that means we can run the Android emulator (which requires KVM) on GCE and at least get fast trybots and such for android-amd64. Updates golang/go#23824 Change-Id: I0da38c7fa0f15492230a31291d2921ba72f2151d Reviewed-on: https://go-review.googlesource.com/c/163738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:35:29 +03:00
})
addBuilder(BuildConfig{
dashboard: add Android trybots Updates golang/go#23824 Change-Id: I6386bc267c35856858b3e46d0998fb60e3406e02 Reviewed-on: https://go-review.googlesource.com/c/build/+/172798 Reviewed-by: Elias Naur <mail@eliasnaur.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-04-18 22:45:32 +03:00
Name: "android-amd64-emu",
dashboard: rename host-android-amd64-emu to host-linux-amd64-androidemu This follows the name convention and avoids a HostArch line. For golang/go#44505. Change-Id: I14654e64751ee830101e1191bd44cd426b3ecce2 Reviewed-on: https://go-review.googlesource.com/c/build/+/420804 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-08-03 22:43:12 +03:00
HostType: "host-linux-amd64-androidemu",
dashboard: configure android-amd64-emu as post-submit only It has been decided in go.dev/issue/53377 for this builder to start being post-submit only. Update the builder configuration accordingly. Keep it as a TryBot only in x/mobile, where its signal should still be a net positive contribution despite the noise in its results. Fixes golang/go#53377. Change-Id: I44ee5454bfe2de15e2f41a82900ee2acc37cd211 Reviewed-on: https://go-review.googlesource.com/c/build/+/407615 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-05-21 00:26:59 +03:00
Notes: "Android emulator on GCE (GOOS=android GOARCH=amd64)",
dashboard: add Android trybots Updates golang/go#23824 Change-Id: I6386bc267c35856858b3e46d0998fb60e3406e02 Reviewed-on: https://go-review.googlesource.com/c/build/+/172798 Reviewed-by: Elias Naur <mail@eliasnaur.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-04-18 22:45:32 +03:00
numTryTestHelpers: 3,
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
tryBot: func(repo, branch, goBranch string) bool {
dashboard: configure android-amd64-emu as post-submit only It has been decided in go.dev/issue/53377 for this builder to start being post-submit only. Update the builder configuration accordingly. Keep it as a TryBot only in x/mobile, where its signal should still be a net positive contribution despite the noise in its results. Fixes golang/go#53377. Change-Id: I44ee5454bfe2de15e2f41a82900ee2acc37cd211 Reviewed-on: https://go-review.googlesource.com/c/build/+/407615 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-05-21 00:26:59 +03:00
// See discussion in go.dev/issue/53377.
dashboard: add android subrepo trybots too Missing from CL 172798 Updates golang/go#23824 Change-Id: I8f1b09ce8f52b555162b344ceddfbfe88e19ad4e Reviewed-on: https://go-review.googlesource.com/c/build/+/174079 Reviewed-by: Elias Naur <mail@eliasnaur.com> Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-04-26 17:04:00 +03:00
switch repo {
dashboard: configure android-amd64-emu as post-submit only It has been decided in go.dev/issue/53377 for this builder to start being post-submit only. Update the builder configuration accordingly. Keep it as a TryBot only in x/mobile, where its signal should still be a net positive contribution despite the noise in its results. Fixes golang/go#53377. Change-Id: I44ee5454bfe2de15e2f41a82900ee2acc37cd211 Reviewed-on: https://go-review.googlesource.com/c/build/+/407615 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-05-21 00:26:59 +03:00
case "mobile":
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
return true
dashboard: add android subrepo trybots too Missing from CL 172798 Updates golang/go#23824 Change-Id: I8f1b09ce8f52b555162b344ceddfbfe88e19ad4e Reviewed-on: https://go-review.googlesource.com/c/build/+/174079 Reviewed-by: Elias Naur <mail@eliasnaur.com> Run-TryBot: Elias Naur <mail@eliasnaur.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-04-26 17:04:00 +03:00
}
return false
cmd/coordinator: test x/mobile on android emu builders; and exp on some Updates golang/go#23824 Change-Id: Iee70bcbfef6a271fdd26694d848a703a200dc0c0 Reviewed-on: https://go-review.googlesource.com/c/164478 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-28 20:32:45 +03:00
},
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b := buildRepoByDefault(repo)
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
switch repo {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
case "mobile":
b = true
dashboard: stop testing x/build on even more builders Follow up to CL 210378 after looking at: https://build.golang.org/?repo=golang.org%2fx%2fbuild Updates golang/go#30640 Change-Id: I81505a9ca2985ffa6e75922665b14ef4de2af860 Reviewed-on: https://go-review.googlesource.com/c/build/+/211100 Reviewed-by: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-12-12 20:43:59 +03:00
case "build", "blog", "talks", "review", "tour", "website":
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
b = false
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
}
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
return b
dashboard: add a GOOS=linux builder & trybot for Android Updates golang/go#30482 Change-Id: I198dd40dfdb86b20e681c373141754680351e82f Reviewed-on: https://go-review.googlesource.com/c/164740 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Elias Naur <mail@eliasnaur.com>
2019-03-01 19:54:25 +03:00
},
env/android-amd64-emu: add new Android emulator container + VM image Now that we can do nested virtualization on GCE, that means we can run the Android emulator (which requires KVM) on GCE and at least get fast trybots and such for android-amd64. Updates golang/go#23824 Change-Id: I0da38c7fa0f15492230a31291d2921ba72f2151d Reviewed-on: https://go-review.googlesource.com/c/163738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:35:29 +03:00
env: []string{
"GOARCH=amd64",
"GOOS=android",
"GOHOSTARCH=amd64",
"GOHOSTOS=linux",
"CGO_ENABLED=1",
},
dashboard: add known issues for android-*-emu Issue golang/go#42212 manifests as test timeouts, and is by far the most frequent of these known issues. Issue golang/go#51001 causes failures with "systemstack called from unexpected goroutine". It seems to have been introduced sometime last year, but it isn't clear to me whether it is a regression or an older (latent) bug unearthed by some other change. Issue golang/go#52724 appears to be a bug or race in the Android emulator itself. It might require a builder image update and/or escalation to the maintainers of the emulator proper. Updates golang/go#53377. Change-Id: I677915b1ff02dd02e0f14c63b0d25caf11e27a72 Reviewed-on: https://go-review.googlesource.com/c/build/+/412174 Reviewed-by: David Chase <drchase@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com>
2022-06-14 22:17:34 +03:00
KnownIssues: []int{42212, 51001, 52724},
env/android-amd64-emu: add new Android emulator container + VM image Now that we can do nested virtualization on GCE, that means we can run the Android emulator (which requires KVM) on GCE and at least get fast trybots and such for android-amd64. Updates golang/go#23824 Change-Id: I0da38c7fa0f15492230a31291d2921ba72f2151d Reviewed-on: https://go-review.googlesource.com/c/163738 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:35:29 +03:00
})
dashboard: add interim illumos builder While the work to make illumos a first class GCE guest is completed, use this interim zone provided by an illumos community member to run illumos builds. Updates golang/go#15581 Change-Id: I1784847e5407894d01ce0aadf489b38d7e5c1924 Reviewed-on: https://go-review.googlesource.com/c/build/+/201597 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-17 11:48:13 +03:00
addBuilder(BuildConfig{
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
Name: "illumos-amd64",
HostType: "host-illumos-amd64-jclulow",
dashboard: add interim illumos builder While the work to make illumos a first class GCE guest is completed, use this interim zone provided by an illumos community member to run illumos builds. Updates golang/go#15581 Change-Id: I1784847e5407894d01ce0aadf489b38d7e5c1924 Reviewed-on: https://go-review.googlesource.com/c/build/+/201597 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-17 11:48:13 +03:00
})
x/build: add Solaris amd64 release builder to dashboard Fixes golang/go#20949 Change-Id: I4f85ee76783a1240a2ebd4a2a1f167ab849fcebe Reviewed-on: https://go-review.googlesource.com/47811 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-07 23:41:20 +03:00
addBuilder(BuildConfig{
dashboard: add known issue for solaris-amd64-oraclerel For golang/go#52653. Updates golang/go#51443. Change-Id: Iaea8fab13ed979e54c827f0f3c4d705bdaff4ee4 Reviewed-on: https://go-review.googlesource.com/c/build/+/408701 Reviewed-by: Alex Rakoczy <alex@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-05-26 18:38:12 +03:00
Name: "solaris-amd64-oraclerel",
dashboard: unrename some reverse builders These names are baked into stage0 or into other custom host configuration controlled by our reverse builder maintainers, which is too hard to update. Live with the old names instead. For #44505. Change-Id: Ia3fdf8fb1c211d3e3fd30a30469571e800ebfe56 Reviewed-on: https://go-review.googlesource.com/c/build/+/420803 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2022-08-03 22:27:33 +03:00
HostType: "host-solaris-oracle-amd64-oraclerel",
dashboard: add known issue for solaris-amd64-oraclerel For golang/go#52653. Updates golang/go#51443. Change-Id: Iaea8fab13ed979e54c827f0f3c4d705bdaff4ee4 Reviewed-on: https://go-review.googlesource.com/c/build/+/408701 Reviewed-by: Alex Rakoczy <alex@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-05-26 18:38:12 +03:00
Notes: "Oracle Solaris release version",
FlakyNet: true,
KnownIssues: []int{51443},
x/build: add Solaris amd64 release builder to dashboard Fixes golang/go#20949 Change-Id: I4f85ee76783a1240a2ebd4a2a1f167ab849fcebe Reviewed-on: https://go-review.googlesource.com/47811 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-07 23:41:20 +03:00
})
all: add ppc64 (big endian) builders Change-Id: I0fddda33179555a50b6f03dcff13338544b742c3 Reviewed-on: https://go-review.googlesource.com/30599 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-10-06 23:30:58 +03:00
addBuilder(BuildConfig{
build/dashboard: add linux-ppc64-sid for testing/upgrade new builder for testing OS upgrade Change-Id: I54b7ace3fbfa6805d7d885fd649efedcd68b01c9 Reviewed-on: https://go-review.googlesource.com/c/build/+/426234 Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Paul Murphy <murp@ibm.com>
2022-08-28 05:20:20 +03:00
Name: "linux-ppc64-sid-buildlet",
HostType: "host-linux-ppc64-sid",
FlakyNet: true,
distTestAdjust: ppc64DistTestPolicy,
env: []string{"GO_TEST_TIMEOUT_SCALE=2"}, // see go.dev/issues/44422
})
dashboard: add solaris, ppc64le, s390x reverse buildlets Change-Id: I5061ae1da7884ed82786e8a042e966ccbe423e89 Reviewed-on: https://go-review.googlesource.com/20135 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-03-01 07:49:24 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "linux-ppc64le-buildlet",
HostType: "host-linux-ppc64le-osu",
FlakyNet: true,
distTestAdjust: ppc64DistTestPolicy,
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
env: []string{"GO_TEST_TIMEOUT_SCALE=2"}, // see go.dev/issues/44422
dashboard: add arm64 buildlet, update ppc64 buildlet definition Change-Id: I25c6de0f97c3338f9d32f4125b2c7c68c3f3c13c Reviewed-on: https://go-review.googlesource.com/21656 Reviewed-by: David Crawshaw <crawshaw@golang.org>
2016-04-07 22:27:15 +03:00
})
dashboard: add linux-ppc64le POWER9 builder This change adds an extra linux-ppc64le builder running on POWER9. Fixes golang/go#30138 Change-Id: I23bdfc116bb89c6d96be330c2c87827c47705b6b Reviewed-on: https://go-review.googlesource.com/c/163757 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:05:12 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "linux-ppc64le-power9osu",
HostType: "host-linux-ppc64le-power9-osu",
FlakyNet: true,
distTestAdjust: ppc64DistTestPolicy,
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
env: []string{"GO_TEST_TIMEOUT_SCALE=2"}, // see go.dev/issues/44422
dashboard: add linux-ppc64le POWER9 builder This change adds an extra linux-ppc64le builder running on POWER9. Fixes golang/go#30138 Change-Id: I23bdfc116bb89c6d96be330c2c87827c47705b6b Reviewed-on: https://go-review.googlesource.com/c/163757 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-02-25 23:05:12 +03:00
})
all: add linux-ppc64le-power10-osu builder This builder requires a patched bootstrap toolchain to accept GOPPC64=power10. Likewise, this folds in a change to update the container images to ubuntu 20.04. This is and has been running on the existing ppc64le builders for a couple months already. Change-Id: Ia86cb711c99c0d8ab5f9de0ae50129fe11e6ccab Reviewed-on: https://go-review.googlesource.com/c/build/+/454515 Run-TryBot: Paul Murphy <murp@ibm.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org>
2022-12-01 01:50:25 +03:00
addBuilder(BuildConfig{
Name: "linux-ppc64le-power10osu",
HostType: "host-linux-ppc64le-power10-osu",
FlakyNet: true,
distTestAdjust: ppc64DistTestPolicy,
env: []string{"GO_TEST_TIMEOUT_SCALE=2"}, // see go.dev/issues/44422
dashboard: restrict linux-ppc64le-power10-osu to go1.20 and newer GOPPC64=power10 is only supported by go1.20 and newer. Don't use this builder with older releases. Change-Id: I5dc012165fce32f13aa8316b54f0fbe9ef337b61 Reviewed-on: https://go-review.googlesource.com/c/build/+/456695 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Paul Murphy <murp@ibm.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Than McIntosh <thanm@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-12-10 02:53:40 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return atLeastGo1(goBranch, 20) && buildRepoByDefault(repo)
},
all: add linux-ppc64le-power10-osu builder This builder requires a patched bootstrap toolchain to accept GOPPC64=power10. Likewise, this folds in a change to update the container images to ubuntu 20.04. This is and has been running on the existing ppc64le builders for a couple months already. Change-Id: Ia86cb711c99c0d8ab5f9de0ae50129fe11e6ccab Reviewed-on: https://go-review.googlesource.com/c/build/+/454515 Run-TryBot: Paul Murphy <murp@ibm.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org>
2022-12-01 01:50:25 +03:00
})
dashboard: add host-linux-arm64-aws builder Add the host-linux-arm64-aws builder. The HostConfig IsVM method has been modified to support the concept that an EC2 VM can be created which runs the buildlet binary in a container. This configuration would have both a VM image and a container image set in the host configuration. For golang/go#36841 Change-Id: I092b48b1dda24d24bcd0b10dff0b2126f5f43017 Reviewed-on: https://go-review.googlesource.com/c/build/+/249118 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-18 20:32:05 +03:00
addBuilder(BuildConfig{
all: replace linux-arm64-aws with linux-arm64 This change replaces linux-arm64-aws with linux-arm64. The new builder runs on GCP and has an increased set of resources. This should provide a performance improvement. The builder will now be used: - To release linux-arm64 - As the linux-arm64 trybot Fixes golang/go#53851 Updates golang/go#54679 Updates golang/go#40561 Change-Id: I9abfe2ed1d1bd8a68bba1e1f924637e829026e6d Reviewed-on: https://go-review.googlesource.com/c/build/+/449615 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-11-10 22:47:04 +03:00
Name: "linux-arm64-aws",
HostType: "host-linux-arm64-aws",
dashboard: add host-linux-arm64-aws builder Add the host-linux-arm64-aws builder. The HostConfig IsVM method has been modified to support the concept that an EC2 VM can be created which runs the buildlet binary in a container. This configuration would have both a VM image and a container image set in the host configuration. For golang/go#36841 Change-Id: I092b48b1dda24d24bcd0b10dff0b2126f5f43017 Reviewed-on: https://go-review.googlesource.com/c/build/+/249118 Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-08-18 20:32:05 +03:00
})
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
addBuilder(BuildConfig{
all: replace linux-arm64-aws with linux-arm64 This change replaces linux-arm64-aws with linux-arm64. The new builder runs on GCP and has an increased set of resources. This should provide a performance improvement. The builder will now be used: - To release linux-arm64 - As the linux-arm64 trybot Fixes golang/go#53851 Updates golang/go#54679 Updates golang/go#40561 Change-Id: I9abfe2ed1d1bd8a68bba1e1f924637e829026e6d Reviewed-on: https://go-review.googlesource.com/c/build/+/449615 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Jenny Rakoczy <jenny@golang.org>
2022-11-10 22:47:04 +03:00
Name: "linux-arm64",
HostType: "host-linux-arm64-bullseye",
tryBot: defaultTrySet(),
numTryTestHelpers: 1,
dashboard, buildlet: add support for ARM64 COS images This adds the ability to query for COS images which are ARM64 based. The HostConfig has been updated to provide the ability to note that a host requires an ARM64 COS image. Updates golang/go#53851 Change-Id: Ib57bf6359ca365078528dbb6912dca2402939df9 Reviewed-on: https://go-review.googlesource.com/c/build/+/447259 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-11-01 23:57:01 +03:00
})
dashboard: add linux-arm64-boringcrypto builder CL 423362 adds boringcrypto support for linux/arm64. Add a builder configuration to test that. Because the builder is on AWS, and because there's essentially no architecture variation in boringcrypto, this builder can be left out of the trybot set: the linux-amd64-boringcrypto trybot will catch boringcrypto issues, and the linux-arm64-aws trybot will catch non-boringcrypto arm64 issues. Any arm64-specific boringcrypto can be dealt with via slowbot or by finding out on the dashboard post-submit for now. Change-Id: Ic257ec02baece554cc178155133706f4d43a7ada Reviewed-on: https://go-review.googlesource.com/c/build/+/423574 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-13 15:49:10 +03:00
addBuilder(BuildConfig{
Name: "linux-arm64-boringcrypto",
HostType: "host-linux-arm64-aws",
env: []string{
"GOEXPERIMENT=boringcrypto",
"GO_DISABLE_OUTBOUND_NETWORK=1",
},
dashboard: replace GoDeps with release branch filters relui doesn't evaluate GoDeps when deciding what builders apply to which release branches, and at this point they're all in the past release anyway. For golang/go#48523. Change-Id: I9d1e89ec7583bbc82712fe946a5e9122e67b66b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/435498 Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:39:27 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return atLeastGo1(goBranch, 19) && buildRepoByDefault(repo)
dashboard: add linux-arm64-boringcrypto builder CL 423362 adds boringcrypto support for linux/arm64. Add a builder configuration to test that. Because the builder is on AWS, and because there's essentially no architecture variation in boringcrypto, this builder can be left out of the trybot set: the linux-amd64-boringcrypto trybot will catch boringcrypto issues, and the linux-arm64-aws trybot will catch non-boringcrypto arm64 issues. Any arm64-specific boringcrypto can be dealt with via slowbot or by finding out on the dashboard post-submit for now. Change-Id: Ic257ec02baece554cc178155133706f4d43a7ada Reviewed-on: https://go-review.googlesource.com/c/build/+/423574 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-08-13 15:49:10 +03:00
},
})
dashboard: add linux-arm64-longtest builder For golang/go#49649. Updates golang/go#53851. Change-Id: Ifbfd2b089b909542d0568d529ba738e4b217cf5c Reviewed-on: https://go-review.googlesource.com/c/build/+/452858 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-11-23 05:02:38 +03:00
addBuilder(BuildConfig{
Name: "linux-arm64-longtest",
all: add additional storage to linux-arm64-longtest builder This adds the ability to set the size of the root drive for a GCE host machine. The linux-arm64-longtest boot disk has been increased from 10GB to 20GB. Updates golang/go#49649 Change-Id: I74ebf4bd533c91c8716b7df167afacbfdded3ed3 Reviewed-on: https://go-review.googlesource.com/c/build/+/453955 Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-11-29 19:51:40 +03:00
HostType: "host-linux-arm64-bullseye-high-disk",
dashboard: add linux-arm64-longtest builder For golang/go#49649. Updates golang/go#53851. Change-Id: Ifbfd2b089b909542d0568d529ba738e4b217cf5c Reviewed-on: https://go-review.googlesource.com/c/build/+/452858 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-11-23 05:02:38 +03:00
Notes: "Debian Bullseye with go test -short=false",
dashboard: enable linux-arm64-longtest builder on 1.20+ release branches From the dashboard, it seems the linux-arm64-longtest builder has been working reasonably well for a while. At this point we don't have known issues for it. So remove known issues. Enable it for trybot on 1.20+ release branches, per golang/go#37827. Only for 1.20+ because it is failing on older versions of Go. Fixes golang/go#49649. Updates golang/go#53851, golang/go#37827. Change-Id: I682aa4028b791ecd80360fbe05ef615dad19405d Reviewed-on: https://go-review.googlesource.com/c/build/+/456043 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-12-09 01:54:27 +03:00
tryBot: func(repo, branch, goBranch string) bool {
onReleaseBranch := strings.HasPrefix(branch, "release-branch.")
return repo == "go" && onReleaseBranch // See issue 37827.
},
dashboard: add linux-arm64-longtest builder For golang/go#49649. Updates golang/go#53851. Change-Id: Ifbfd2b089b909542d0568d529ba738e4b217cf5c Reviewed-on: https://go-review.googlesource.com/c/build/+/452858 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-11-23 05:02:38 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: enable linux-arm64-longtest builder on 1.20+ release branches From the dashboard, it seems the linux-arm64-longtest builder has been working reasonably well for a while. At this point we don't have known issues for it. So remove known issues. Enable it for trybot on 1.20+ release branches, per golang/go#37827. Only for 1.20+ because it is failing on older versions of Go. Fixes golang/go#49649. Updates golang/go#53851, golang/go#37827. Change-Id: I682aa4028b791ecd80360fbe05ef615dad19405d Reviewed-on: https://go-review.googlesource.com/c/build/+/456043 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-12-09 01:54:27 +03:00
b := atLeastGo1(goBranch, 20) && buildRepoByDefault(repo)
dashboard: add linux-arm64-longtest builder For golang/go#49649. Updates golang/go#53851. Change-Id: Ifbfd2b089b909542d0568d529ba738e4b217cf5c Reviewed-on: https://go-review.googlesource.com/c/build/+/452858 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Cherry Mui <cherryyz@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-11-23 05:02:38 +03:00
if repo != "go" && !(branch == "master" && goBranch == "master") {
// For golang.org/x repos, don't test non-latest versions.
b = false
}
return b
},
needsGoProxy: true, // for cmd/go module tests
env: []string{
"GO_TEST_TIMEOUT_SCALE=5", // give them lots of time
},
numTryTestHelpers: 4, // Target time is < 15 min for go.dev/issue/42661.
})
env/linux-arm/aws, dashboard: add linux-arm-aws builder This change adds the linux-arm-aws builder. This builder will be started on a EC2 instance which will spawn a single instance of the container. After the builder work is done, the instance will be destroyed. Updates golang/go#41867 Change-Id: I09d911c2f99d1dff8fe02feb458457e07e7d0cdd Reviewed-on: https://go-review.googlesource.com/c/build/+/260797 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-10-08 23:49:48 +03:00
addBuilder(BuildConfig{
dashboard: add linux-arm-aws to trybots This change adds linux-arm-aws to the set of trybots. The related changes include: - Renaming the linux-arm builder to linux-arm-scaleway. - Adding slowbot aliases which use linux-arm-aws as the default builder for linux-arm builds. Fixes golang/go#35628 Fixes golang/go#40872 Updates golang/go#45064 Change-Id: Ib49f50e03fc4f766015fdd78080b804c2784a398 Reviewed-on: https://go-review.googlesource.com/c/build/+/303230 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-03-19 20:54:17 +03:00
Name: "linux-arm-aws",
HostType: "host-linux-arm-aws",
tryBot: defaultTrySet(),
numTryTestHelpers: 1,
dashboard: set GO{,HOST}ARCH, GOARM on linux-arm-aws builder This change modifies the environmental variables for the linux-arm-aws builder. It standardizes the environment that the linux/arm is tested and released on. Fixes golang/go#47554 Change-Id: Ie96ad93be20434636f29ab9c778fbed12fdb8d82 Reviewed-on: https://go-review.googlesource.com/c/build/+/340112 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-05 18:02:29 +03:00
env: []string{
"GOARCH=arm",
"GOARM=6",
"GOHOSTARCH=arm",
dashboard: set -march=armv6 on linux-arm-aws This is currently set directly in cmd/release, which means we're not testing what we're releasing. With this done, we no longer need special handling in cmd/release. Updates golang/go#18748. Change-Id: Ib9bd19a2a07e98f64c0169d5d31976c7c61f656f Reviewed-on: https://go-review.googlesource.com/c/build/+/390395 Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Trust: Heschi Kreinick <heschi@google.com>
2022-03-07 18:11:24 +03:00
"CGO_CFLAGS=-march=armv6",
"CGO_LDFLAGS=-march=armv6",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=2", // inherited from cmd/dist's default for GOARCH=arm
dashboard: set GO{,HOST}ARCH, GOARM on linux-arm-aws builder This change modifies the environmental variables for the linux-arm-aws builder. It standardizes the environment that the linux/arm is tested and released on. Fixes golang/go#47554 Change-Id: Ie96ad93be20434636f29ab9c778fbed12fdb8d82 Reviewed-on: https://go-review.googlesource.com/c/build/+/340112 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-05 18:02:29 +03:00
},
env/linux-arm/aws, dashboard: add linux-arm-aws builder This change adds the linux-arm-aws builder. This builder will be started on a EC2 instance which will spawn a single instance of the container. After the builder work is done, the instance will be destroyed. Updates golang/go#41867 Change-Id: I09d911c2f99d1dff8fe02feb458457e07e7d0cdd Reviewed-on: https://go-review.googlesource.com/c/build/+/260797 Trust: Carlos Amedee <carlos@golang.org> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-10-08 23:49:48 +03:00
})
dashboard: add linux-loong64-3a5000 builder Updates golang/go#46229 Change-Id: Ib48e1e64d96a07d5c5282d78935124faf75c89d7 Reviewed-on: https://go-review.googlesource.com/c/build/+/347309 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Cherry Mui <cherryyz@google.com>
2021-09-02 10:51:28 +03:00
addBuilder(BuildConfig{
dashboard: mark loong64 builder as having flaky networks For golang/go#46229 Change-Id: I13180d6920d2824adbe2d25ad55b6ae985e95d8f Reviewed-on: https://go-review.googlesource.com/c/build/+/397515 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Trust: Tobias Klauser <tobias.klauser@gmail.com>
2022-04-01 05:40:26 +03:00
FlakyNet: true,
dashboard: add linux-loong64-3a5000 builder Updates golang/go#46229 Change-Id: Ib48e1e64d96a07d5c5282d78935124faf75c89d7 Reviewed-on: https://go-review.googlesource.com/c/build/+/347309 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Cherry Mui <cherryyz@google.com>
2021-09-02 10:51:28 +03:00
HostType: "host-linux-loong64-3a5000",
Name: "linux-loong64-3a5000",
SkipSnapshot: true,
distTestAdjust: loong64DistTestPolicy,
buildsRepo: loong64BuildsRepoPolicy,
dashboard: add privateGoProxy setting for linux-loong64-3a5000 Because these builders are behind the firewall, they may not access to proxy.golang.org, but it has a private Go module proxy. For golang/go#46229. Change-Id: Ib125cdaafca465f85531750cb9f5eb36d54f02de Reviewed-on: https://go-review.googlesource.com/c/build/+/408434 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-05-25 10:55:11 +03:00
privateGoProxy: true, // this builder is behind firewall
dashboard: add linux-loong64-3a5000 builder Updates golang/go#46229 Change-Id: Ib48e1e64d96a07d5c5282d78935124faf75c89d7 Reviewed-on: https://go-review.googlesource.com/c/build/+/347309 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Cherry Mui <cherryyz@google.com>
2021-09-02 10:51:28 +03:00
env: []string{
"GOARCH=loong64",
"GOHOSTARCH=loong64",
},
dashboard: add known issues for linux/loong64 (This will cause 'greplogs --triage' to filter out this builder by default.) Updates golang/go#53116. Change-Id: Ib238c641b83f6aec3d1fd75933b7d8593313da21 Reviewed-on: https://go-review.googlesource.com/c/build/+/408938 Reviewed-by: Alex Rakoczy <alex@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-05-27 18:50:53 +03:00
KnownIssues: []int{53116, 53093},
dashboard: add linux-loong64-3a5000 builder Updates golang/go#46229 Change-Id: Ib48e1e64d96a07d5c5282d78935124faf75c89d7 Reviewed-on: https://go-review.googlesource.com/c/build/+/347309 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Cherry Mui <cherryyz@google.com>
2021-09-02 10:51:28 +03:00
})
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
FlakyNet: true,
HostType: "host-linux-mips64le-rtrk",
Name: "linux-mips64le-rtrk",
SkipSnapshot: true,
distTestAdjust: mipsDistTestPolicy,
buildsRepo: mipsBuildsRepoPolicy,
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
env: []string{
"GOARCH=mips64le",
"GOHOSTARCH=mips64le",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=4", // inherited from cmd/dist's default for GOARCH=mips{,le,64,64le}
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
},
})
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
FlakyNet: true,
HostType: "host-linux-mips64le-rtrk",
Name: "linux-mipsle-rtrk",
SkipSnapshot: true,
distTestAdjust: mipsDistTestPolicy,
buildsRepo: mipsBuildsRepoPolicy,
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
env: []string{
"GOARCH=mipsle",
"GOHOSTARCH=mipsle",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=4", // inherited from cmd/dist's default for GOARCH=mips{,le,64,64le}
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
},
})
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
FlakyNet: true,
HostType: "host-linux-mips64-rtrk",
Name: "linux-mips64-rtrk",
SkipSnapshot: true,
distTestAdjust: mipsDistTestPolicy,
buildsRepo: mipsBuildsRepoPolicy,
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
env: []string{
"GOARCH=mips64",
"GOHOSTARCH=mips64",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=4", // inherited from cmd/dist's default for GOARCH=mips{,le,64,64le}
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
},
})
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
FlakyNet: true,
HostType: "host-linux-mips64-rtrk",
Name: "linux-mips-rtrk",
SkipSnapshot: true,
distTestAdjust: mipsDistTestPolicy,
buildsRepo: mipsBuildsRepoPolicy,
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
env: []string{
"GOARCH=mips",
"GOHOSTARCH=mips",
dashboard: apply cmd/dist's timeout scale for arm, mips* architectures These values come from cmd/dist doing it by default based on GOARCH. We want to factor out that logic from cmd/dist, so apply it explicitly in x/build to appropriate builders. CL 455518 removes it from cmd/dist. The appropriate builders were found by iterating over all builders in this package and filtering on their GOARCH value. For golang/go#56968. For golang/go#57117. Change-Id: I1bccb7144d9ae13ca17e5f12169924d0fb89e341 Reviewed-on: https://go-review.googlesource.com/c/build/+/455521 Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
2022-12-05 23:33:01 +03:00
"GO_TEST_TIMEOUT_SCALE=4", // inherited from cmd/dist's default for GOARCH=mips{,le,64,64le}
dashboard: add linux-mipsle-mengzhuo builder Updates golang/go#31217 Change-Id: I7bda4f3ddf7dc76bdd974726747621f69a7acfa0 Reviewed-on: https://go-review.googlesource.com/c/build/+/191577 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-09-10 02:21:11 +03:00
},
dashboard: add linux-riscv64-jsing builder (reverse) Also use this as the riscv64 slowbot, since linux-riscv64-unleashed has been MIA for quite some time. For golang/go#27532 Change-Id: I01309a66b96d4c35dbc9d1e08f55f5357b0acba0 Reviewed-on: https://go-review.googlesource.com/c/build/+/257917 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-09-27 21:25:41 +03:00
})
addBuilder(BuildConfig{
dashboard: disable api/reboot test for unmatched It takes >15m to complete api and reboot tests for Hifive unmatched which we don't need. Change-Id: Ie4535264d2e8ef4496c54fb5f412d5ec773f538a Reviewed-on: https://go-review.googlesource.com/c/build/+/346709 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-09-01 10:08:03 +03:00
HostType: "host-linux-riscv64-joelsing",
Name: "linux-riscv64-jsing",
SkipSnapshot: true,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: disable api/reboot test for unmatched It takes >15m to complete api and reboot tests for Hifive unmatched which we don't need. Change-Id: Ie4535264d2e8ef4496c54fb5f412d5ec773f538a Reviewed-on: https://go-review.googlesource.com/c/build/+/346709 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-09-01 10:08:03 +03:00
env: []string{"GO_TEST_TIMEOUT_SCALE=4"},
distTestAdjust: riscvDistTestPolicy,
dashboard: add linux-riscv64-jsing builder (reverse) Also use this as the riscv64 slowbot, since linux-riscv64-unleashed has been MIA for quite some time. For golang/go#27532 Change-Id: I01309a66b96d4c35dbc9d1e08f55f5357b0acba0 Reviewed-on: https://go-review.googlesource.com/c/build/+/257917 Trust: Joel Sing <joel@sing.id.au> Run-TryBot: Joel Sing <joel@sing.id.au> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-09-27 21:25:41 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
switch repo {
case "go", "net", "sys":
dashboard, cmd/coordinator: add linux-riscv64 builder, fix bug from CL 205608 Updates golang/go#27532 Updates golang/go#30262 Change-Id: If1593ab6e5653a9dce625f25a16bf8a082796592 Reviewed-on: https://go-review.googlesource.com/c/build/+/206639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-11-12 09:19:21 +03:00
return branch == "master" && goBranch == "master"
default:
return false
}
},
})
dashboard: add linux-riscv64-unmatched This adds a reverse buildlet for linux riscv64 running under Hifive Unmatched. For golang/go#46804. Change-Id: If5ed8b47205cecebcb90a4d1b03c463e1eb466c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/329489 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-27 07:26:14 +03:00
addBuilder(BuildConfig{
dashboard: disable api/reboot test for unmatched It takes >15m to complete api and reboot tests for Hifive unmatched which we don't need. Change-Id: Ie4535264d2e8ef4496c54fb5f412d5ec773f538a Reviewed-on: https://go-review.googlesource.com/c/build/+/346709 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-09-01 10:08:03 +03:00
HostType: "host-linux-riscv64-unmatched",
Name: "linux-riscv64-unmatched",
dashboard: skip perf test for linux-riscv64-unmatched The perf test still timeed out even CL 417314 increased builder timeout scale up to 6. Unfortunately we had to skip this test for now and revert timeout scale back to 4. For golang/go#53745 Change-Id: I247179b42c575ca05bb0ec6b51d260ab51d912f3 Reviewed-on: https://go-review.googlesource.com/c/build/+/417495 Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-07-14 14:01:17 +03:00
env: []string{"GO_TEST_TIMEOUT_SCALE=4"},
dashboard: disable api/reboot test for unmatched It takes >15m to complete api and reboot tests for Hifive unmatched which we don't need. Change-Id: Ie4535264d2e8ef4496c54fb5f412d5ec773f538a Reviewed-on: https://go-review.googlesource.com/c/build/+/346709 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-09-01 10:08:03 +03:00
FlakyNet: true,
distTestAdjust: riscvDistTestPolicy,
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
privateGoProxy: true, // this builder is behind firewall
dashboard: skip perf test for linux-riscv64-unmatched The perf test still timeed out even CL 417314 increased builder timeout scale up to 6. Unfortunately we had to skip this test for now and revert timeout scale back to 4. For golang/go#53745 Change-Id: I247179b42c575ca05bb0ec6b51d260ab51d912f3 Reviewed-on: https://go-review.googlesource.com/c/build/+/417495 Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-07-14 14:01:17 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// see https://go.dev/issue/53745
if repo == "perf" {
return false
}
return onlyMasterDefault(repo, branch, goBranch)
},
dashboard: add linux-riscv64-unmatched This adds a reverse buildlet for linux riscv64 running under Hifive Unmatched. For golang/go#46804. Change-Id: If5ed8b47205cecebcb90a4d1b03c463e1eb466c7 Reviewed-on: https://go-review.googlesource.com/c/build/+/329489 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-08-27 07:26:14 +03:00
})
dashboard: add solaris, ppc64le, s390x reverse buildlets Change-Id: I5061ae1da7884ed82786e8a042e966ccbe423e89 Reviewed-on: https://go-review.googlesource.com/20135 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-03-01 07:49:24 +03:00
addBuilder(BuildConfig{
Name: "linux-s390x-ibm",
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
HostType: "host-linux-s390x",
cmd/coordinator, dashboard: remove some trybots, shard others wider I'm aiming to have trybot runs finish in under 5 minutes. This CL removes openbsd-386-gce58 and freebsd-386-gce101 from the trybot set. openbsd-386-gce58 is the slowest builder. It has an average speed of 722 seconds (and 95 percentile of 923 seconds) over the past week, and that's sharded over 4 machines. Too slow. It's not worth the resources to keep it as a trybot. It hasn't caught any interesting bugs. This builder will still run, but not as a pre-submit trybot. freebsd-386-gce101 is not slow, but we're removing it to shift its resources to shard other builders wider. The coordinator now supports varying the build sharding width based on whether a build is for a trybot or not. This CL defines separate numbers for each, sharding builds wider as needed for some trybots. freebsd-amd64-gce101 goes from 4 to 5 machines in try runs, and down to 3 when not in try runs. linux-amd64-race gets one more machine during try runs, and one fewer in regular runs. linux-arm goes from 7 machines always, to 3 or 8, depending on whether it's a try run. openbsd-amd64-58 goes from 4 to 3 or 6. windows-amd64-gce goes from 4 to 2 or 6. windows-amd64-race goes from 4 to 2 or 6. darwin-amd64-10_11 goes from 3 to 3 or 4. I'll see how these do over the next few days and readjust as needed. Also in this CL: fix the constants for the expected duration of make.bash, which impact when we schedule the creation of test sharding helper buildlets. We were creating them too early before, wasting resources. Change-Id: I38a9b24841e196f1eb668de058c49af8c1d1c64f Reviewed-on: https://go-review.googlesource.com/29116 Reviewed-by: Quentin Smith <quentin@golang.org>
2016-09-14 01:45:48 +03:00
numTestHelpers: 0,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: add solaris, ppc64le, s390x reverse buildlets Change-Id: I5061ae1da7884ed82786e8a042e966ccbe423e89 Reviewed-on: https://go-review.googlesource.com/20135 Reviewed-by: Andrew Gerrand <adg@golang.org>
2016-03-01 07:49:24 +03:00
})
dashboard: add s390x cross-compile-only builder and release config Also modifies cmd/release to wire it up. Updates golang/go#16443 Change-Id: Ie80a224957f6f662d0aec0fd083e2a57e30436c4 Reviewed-on: https://go-review.googlesource.com/28172 Reviewed-by: Jessica Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-08-30 23:32:33 +03:00
addBuilder(BuildConfig{
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
Name: "linux-s390x-crosscompile",
dashboard: rename and sort a few more hosts This ensures the hosts have names from which we can derive their GOOS-GOARCH settings. Change-Id: I48a56750b439b0be52b7bfc338ebfe7309617d36 Reviewed-on: https://go-review.googlesource.com/c/build/+/419990 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-07-29 05:41:47 +03:00
HostType: "host-linux-amd64-s390x-cross",
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
Notes: "s390x cross-compile builder for releases; doesn't run tests",
CompileOnly: true,
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
tryOnly: true, // but not in trybot set for now
dashboard: add s390x cross-compile-only builder and release config Also modifies cmd/release to wire it up. Updates golang/go#16443 Change-Id: Ie80a224957f6f662d0aec0fd083e2a57e30436c4 Reviewed-on: https://go-review.googlesource.com/28172 Reviewed-by: Jessica Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-08-30 23:32:33 +03:00
env: []string{
"CGO_ENABLED=1",
"GOARCH=s390x",
"GOHOSTARCH=amd64",
"CC_FOR_TARGET=s390x-linux-gnu-gcc",
},
})
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
addBuilder(BuildConfig{
Name: "linux-amd64-localdev",
HostType: "host-linux-amd64-localdev",
Notes: "for localhost development only",
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
tryOnly: true,
cmd/coordinator, cmd/buildlet, cmd/gomote: add SSH support This adds an SSH server to farmer.golang.org on port 2222 that proxies SSH connections to users' gomote-created buildlet instances. For example: $ gomote create openbsd-amd64-60 user-bradfitz-openbsd-amd64-60-1 $ gomote ssh user-bradfitz-openbsd-amd64-60-1 Warning: Permanently added '[localhost]:33351' (ECDSA) to the list of known hosts. OpenBSD 6.0 (GENERIC.MP) golang/go#2319: Tue Jul 26 13:00:43 MDT 2016 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. $ As before, if the coordinator process is restarted (or crashes, is evicted, etc), all gomote instances die. Not yet supported: * scp (help wanted) * not all host types are configured. most are. some will need slight config tweaks to the Docker image (e.g. adding openssh-server) Supports currently: * linux-amd64 (host type shared by 386, nacl) * linux-arm * linux-arm64 * darwin * freebsd * openbsd * plan9-386 * windows Implementation details: * the ssh server process listens on port 2222 in the coordinator (farmer.golang.org), which is behind a GKE TCP load balancer. * the ssh server library is github.com/gliderlabs/ssh * authentication is done via Github users' public keys. It's assumed that gomote user == github user. But there's a mapping in the code for known exceptions. * we can't give out access to this too widely. too many things are accessible from within the host environment if you look in the right places. Details omitted. But the Go team and other trusted gomote users can use this. * the buildlet binary has a new /connect-ssh handler that acts like a CONNECT request but instead of taking an explicit host:port, just says "give me your machine's SSH connection". The buildlet can also start sshd if needed for the environment. The /connect-ssh handler also installs the coordinator's public key. * a new buildlet client library method "ConnectSSH" hits the /connect-ssh handler and returns a net.Conn. * the coordinator's ssh.Handler is just running the OpenSSH ssh client. * because the OpenSSH ssh child process can't connect to a net.Conn, an emphemeral localhost port is created on the coordinator to proxy between the ssh client and the net.Conn returned by ConnectSSH. * The /connect-ssh handler requires http.Hijacker, which requires fully compliant net.Conn implementations as of Go 1.8. So I needed to flesh out revdial too, testing it with the golang.org/x/net/nettest package. * plan9 doesn't have an ssh server, so we use 0intro's new conterm program (drawterm without GUI support) to connect to plan9 from the coordinator ssh proxy instead of using the OpenSSH ssh client binary. * windows doesn't have an ssh server, so we enable the telnet service and the coordinator ssh proxy uses telnet instead on the backend on the private network. (There is a Windows ssh server but only in new versions.) Happy debugging over ssh! Fixes golang/go#19956 Change-Id: I80a62064c5f85af1f195f980c862ba29af4015f0 Reviewed-on: https://go-review.googlesource.com/50750 Reviewed-by: Herbie Ong <herbie@google.com> Reviewed-by: Jessie Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-07-22 22:15:56 +03:00
})
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
addBuilder(BuildConfig{
dashboard: skip snapshots for dragonfly-amd64-622 This builder is having issues uploading to GCS. Temporarily disable snapshotting for debugging. Change-Id: I780be214d55027fc275ba9358e53466808d744a7 Reviewed-on: https://go-review.googlesource.com/c/build/+/420795 Run-TryBot: Jenny Rakoczy <jenny@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org>
2022-08-03 00:35:37 +03:00
Name: "dragonfly-amd64-622",
HostType: "host-dragonfly-amd64-622",
Notes: "DragonFly BSD 6.2.2, running on GCE",
SkipSnapshot: true,
dashboard: require Go1.20+ for dragonfly Disable dragonfly builder for releases less than Go 1.20 (no need to be doing dragonfly testing given that it is not a primary port). Change-Id: I4aa4ac490efcf0e56d5920d1b4663c27790abad9 Reviewed-on: https://go-review.googlesource.com/c/build/+/423035 Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-08-11 21:16:42 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
return atLeastGo1(goBranch, 20) && buildRepoByDefault(repo)
},
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
})
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "freebsd-arm-paulzhol",
HostType: "host-freebsd-arm-paulzhol",
distTestAdjust: noTestDirAndNoReboot,
SkipSnapshot: true,
dashboard: mark builders with unreliable DNS as flaky These are the builders identified in the logs in golang/go#50191, and associated builders with the same owners (which I assume are likely to employ the same DNS servers). For golang/go#50191 Change-Id: I5906782c6a63a001b0ba1194cffad08de2d8ce6a Reviewed-on: https://go-review.googlesource.com/c/build/+/372294 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-12-15 19:40:12 +03:00
FlakyNet: true,
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// This was a fragile little machine with limited memory.
// Only run a few of the core subrepos for now while
// we figure out what's killing it.
switch repo {
case "go", "sys", "net":
return true
}
return false
},
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
env: []string{
"GOARM=7",
"CGO_ENABLED=1",
dashboard: explicitly set timeout scale in {freebsd,plan9}/arm builders These two builders have GO_TEST_TIMEOUT_SCALE values set in their local environment. Since those variables affect the builder, and will soon be needed for golang.org/x test timeout scale, set them explicitly in the dashboard package. That makes more of the builder configuration visible and removes the need to maintain local configuration on those builders. For golang/go#56968. Change-Id: I206cbddab91c3628f43716e8b05fd52d94fba7f2 Reviewed-on: https://go-review.googlesource.com/c/build/+/455520 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-12-06 21:37:09 +03:00
"GO_TEST_TIMEOUT_SCALE=8", // from builder's local environment as of 2022-12-06
dashboard: update dragonfly-amd64 and freebsd-arm to be buildlet-based Updates golang/go#21191 Change-Id: I636204e9e4cbe77e34b2bbad65312fb6f2ace2dc Reviewed-on: https://go-review.googlesource.com/53490 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-08-06 01:56:18 +03:00
},
})
dashboard: add FreeBSD arm64 builder Updates golang/go#24715 Change-Id: I8eb3f6372d69718b6f453e5415cdf16aa00ccae6 Reviewed-on: https://go-review.googlesource.com/c/build/+/198597 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-10-03 15:56:19 +03:00
addBuilder(BuildConfig{
Name: "freebsd-arm64-dmgk",
HostType: "host-freebsd-arm64-dmgk",
})
build/dashboard: add freebsd-riscv64 Fixes golang/go#53466. Change-Id: Icb95b00ce2f82620add81080a3f6d589586a19ab Reviewed-on: https://go-review.googlesource.com/c/build/+/425937 Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-08-26 22:41:14 +03:00
addBuilder(BuildConfig{
dashboard: update freebsd-riscv64-unmatched for flakynet This builder in a slow uplink network(ADSL) as other builders mengzhuo got. Change-Id: I0992b628984bb417be886e36b5130047e52877ea Reviewed-on: https://go-review.googlesource.com/c/build/+/437975 Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-03 09:17:36 +03:00
Name: "freebsd-riscv64-unmatched",
HostType: "host-freebsd-riscv64-unmatched",
env: []string{"GO_TEST_TIMEOUT_SCALE=4"},
FlakyNet: true,
distTestAdjust: riscvDistTestPolicy,
privateGoProxy: true, // this builder is behind firewall
SkipSnapshot: true, // The builder has a slow uplink bandwidth.
dashbord: restrict freebsd-riscv64-unmatched to the same repos as linux-riscv64-unmatched Fixes golang/go#56273. Updates golang/go#53466. Change-Id: I6e796006f8f7120ae05d5e62cdbc7cdd9d146f7e Reviewed-on: https://go-review.googlesource.com/c/build/+/456575 Auto-Submit: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Run-TryBot: Bryan Mills <bcmills@google.com>
2022-12-09 22:07:32 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
// see https://go.dev/issue/53745
if repo == "perf" {
return false
}
return onlyMasterDefault(repo, branch, goBranch)
},
build/dashboard: add freebsd-riscv64 Fixes golang/go#53466. Change-Id: Icb95b00ce2f82620add81080a3f6d589586a19ab Reviewed-on: https://go-review.googlesource.com/c/build/+/425937 Run-TryBot: David Chase <drchase@google.com> Reviewed-by: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
2022-08-26 22:41:14 +03:00
})
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
addBuilder(BuildConfig{
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
Name: "plan9-arm",
HostType: "host-plan9-arm-0intro",
distTestAdjust: noTestDirAndNoReboot,
dashboard: omit the website repo on plan9 The plan9 builders have relatively slow filesystems, and the website repo is relatively filesystem-intensive — many of its tests walk and process large trees of website content. Instead of trying to precisely tune the x/website tests to pass on the plan9 builders, let's skip this repo on them. For golang/go#49338. Change-Id: Ieaf50fb6955a6b39012a23ff72e61c1c31e4ce7c Reviewed-on: https://go-review.googlesource.com/c/build/+/362975 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-10 19:28:50 +03:00
buildsRepo: plan9Default,
dashboard: add known issue for plan9-arm For golang/go#52653. Updates golang/go#49338. Change-Id: Ib23be56bd79bce8b3168cb40064916a2a91dbb88 Reviewed-on: https://go-review.googlesource.com/c/build/+/408697 Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-05-26 18:18:36 +03:00
KnownIssues: []int{49338},
dashboard: explicitly set timeout scale in {freebsd,plan9}/arm builders These two builders have GO_TEST_TIMEOUT_SCALE values set in their local environment. Since those variables affect the builder, and will soon be needed for golang.org/x test timeout scale, set them explicitly in the dashboard package. That makes more of the builder configuration visible and removes the need to maintain local configuration on those builders. For golang/go#56968. Change-Id: I206cbddab91c3628f43716e8b05fd52d94fba7f2 Reviewed-on: https://go-review.googlesource.com/c/build/+/455520 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com>
2022-12-06 21:37:09 +03:00
env: []string{
"GO_TEST_TIMEOUT_SCALE=3", // from builder's local environment as of 2022-12-06
},
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
})
addBuilder(BuildConfig{
dashboard: rename plan9-amd64-9front builder to plan9-386-0intro The builder name was misleading, because plan9-amd64-9front hasn't been running 9front anymore since 2016, but is running the 9k kernel from Bell Labs. Change-Id: I6929583b784d076a86b818649c64b821a538ed1c Reviewed-on: https://go-review.googlesource.com/c/build/+/307409 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Trust: Carlos Amedee <carlos@golang.org> Trust: David du Colombier <0intro@gmail.com> Run-TryBot: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-04-05 21:42:05 +03:00
Name: "plan9-amd64-0intro",
dashboard: use snapshots on Plan 9 builders This change enables snapshots on Plan 9 builders, so running the tests for each of the golang.org/x repositories will not require to rebuild Go every time. Change-Id: I305b713a48c155ebba2c03f39633d17a6fd71e6f Reviewed-on: https://go-review.googlesource.com/c/build/+/208359 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-11-22 22:19:11 +03:00
HostType: "host-plan9-amd64-0intro",
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
distTestAdjust: func(run bool, distTest string, isNormalTry bool) bool {
run = noTestDirAndNoReboot(run, distTest, isNormalTry)
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
switch distTest {
dashboard: disable cmd/go tests on plan9-amd64-9front The cmd/go tests are timing out on the plan9/amd64 builder because they take more than 20m to complete. This change disables the cmd/go tests on the plan9/amd64 builder, like it was done on the plan9/386 builder. Updates golang/go#31910. Change-Id: I157b472da8498ddce0f641cccb79bc50ae65ca3b Reviewed-on: https://go-review.googlesource.com/c/build/+/175898 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-05-08 20:42:00 +03:00
case "api",
"go_test:cmd/go": // takes over 20 minutes without working SMP
return false
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: disable cmd/go tests on plan9-amd64-9front The cmd/go tests are timing out on the plan9/amd64 builder because they take more than 20m to complete. This change disables the cmd/go tests on the plan9/amd64 builder, like it was done on the plan9/386 builder. Updates golang/go#31910. Change-Id: I157b472da8498ddce0f641cccb79bc50ae65ca3b Reviewed-on: https://go-review.googlesource.com/c/build/+/175898 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
2019-05-08 20:42:00 +03:00
},
dashboard: add known issues for plan9-386, plan9-386-0intro, and plan9-amd64-0intro For golang/go#52653. Updates golang/go#29801. Updates golang/go#49756. Updates golang/go#50137. Change-Id: Ided04da5c1e403c4a194c8c645c5179534a00907 Reviewed-on: https://go-review.googlesource.com/c/build/+/408698 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com>
2022-05-26 18:22:04 +03:00
buildsRepo: plan9Default,
KnownIssues: []int{49756, 49327},
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
})
dashboard: add plan9-386-0intro builder This change adds the plan9-386-0intro builder configuration. Updates golang/go#29801. Change-Id: I5f64f4592a499eb1691498805fd0dfa5082c33d5 Reviewed-on: https://go-review.googlesource.com/c/build/+/175901 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-09 19:52:40 +03:00
addBuilder(BuildConfig{
dashboard: use snapshots on Plan 9 builders This change enables snapshots on Plan 9 builders, so running the tests for each of the golang.org/x repositories will not require to rebuild Go every time. Change-Id: I305b713a48c155ebba2c03f39633d17a6fd71e6f Reviewed-on: https://go-review.googlesource.com/c/build/+/208359 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-11-22 22:19:11 +03:00
Name: "plan9-386-0intro",
HostType: "host-plan9-386-0intro",
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
distTestAdjust: func(run bool, distTest string, isNormalTry bool) bool {
run = noTestDirAndNoReboot(run, distTest, isNormalTry)
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
switch distTest {
dashboard: add plan9-386-0intro builder This change adds the plan9-386-0intro builder configuration. Updates golang/go#29801. Change-Id: I5f64f4592a499eb1691498805fd0dfa5082c33d5 Reviewed-on: https://go-review.googlesource.com/c/build/+/175901 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-09 19:52:40 +03:00
case "api",
"go_test:cmd/go": // takes over 20 minutes without working SMP
return false
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: add plan9-386-0intro builder This change adds the plan9-386-0intro builder configuration. Updates golang/go#29801. Change-Id: I5f64f4592a499eb1691498805fd0dfa5082c33d5 Reviewed-on: https://go-review.googlesource.com/c/build/+/175901 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-09 19:52:40 +03:00
},
dashboard: add known issues for plan9-386, plan9-386-0intro, and plan9-amd64-0intro For golang/go#52653. Updates golang/go#29801. Updates golang/go#49756. Updates golang/go#50137. Change-Id: Ided04da5c1e403c4a194c8c645c5179534a00907 Reviewed-on: https://go-review.googlesource.com/c/build/+/408698 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Alex Rakoczy <alex@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com>
2022-05-26 18:22:04 +03:00
buildsRepo: plan9Default,
KnownIssues: []int{50137, 50878},
dashboard: add plan9-386-0intro builder This change adds the plan9-386-0intro builder configuration. Updates golang/go#29801. Change-Id: I5f64f4592a499eb1691498805fd0dfa5082c33d5 Reviewed-on: https://go-review.googlesource.com/c/build/+/175901 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-05-09 19:52:40 +03:00
})
dashboard: add aix-ppc64 builder This is a starting point for adding an aix-ppc64 reverse builder. There can be further adjustments made to it as needed. Updates golang/go#27160. Change-Id: I8a61adbe21f1a08265df9a206d94bb04e880a508 Reviewed-on: https://go-review.googlesource.com/131335 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-08-24 21:41:05 +03:00
addBuilder(BuildConfig{
dashboard: remove stale "at least Go 1.16" checks In this package, there are uses of atLeastGo1, MinimumGoVersion, GoDeps, and addMiscCompileGo1 to prevent builds from running on Go commits that don't meet the minimum Go version requirement. At this point in time, Go 1.17 and 1.16 are the supported releases, and coordinator doesn't test anything older. Remove various checks from build policies that become redundant due to being always true. Similarly, the misc-compile-darwinarm64 TryBot no longer needs to be special, so we can divide misc-compile TryBot work more evenly. Change-Id: I3a4804d18b1cdff1e46427cd8e73167aa18d8a35 Reviewed-on: https://go-review.googlesource.com/c/build/+/386115 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Trust: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org>
2022-02-16 07:54:15 +03:00
Name: "aix-ppc64",
HostType: "host-aix-ppc64-osuosl",
dashboard: add /opt/freeware/bin to PATH on aix builder Updates golang/go#29065 Fixes golang/go#29078 Change-Id: Ifa9355c9dc988a460b6198913431647ec2c5e6ac Reviewed-on: https://go-review.googlesource.com/c/152457 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-12-04 17:46:08 +03:00
env: []string{
"PATH=/opt/freeware/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java7_64/jre/bin:/usr/java7_64/bin",
},
dashboard: don't build x/net master against Go 1.12 on aix Per request in https://golang.org/issue/31564#issuecomment-484786144 Change-Id: I52e496083b84aa021e7d7cdcda19c96980e1518f Reviewed-on: https://go-review.googlesource.com/c/build/+/172878 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-19 17:37:11 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
switch repo {
dashboard: skip vulndb on aix-ppc64 vulndb currently uses a dependency which does not build cleanly on this os/arch combo. Until that issue is resolved, skip (this code is not intended to be run on a large variety of systems, so it should be fine for the foreseeable future.) Fixes golang/go#49218 Change-Id: I174daf963dbb4493141330bae55398e9f97f0fc1 Reviewed-on: https://go-review.googlesource.com/c/build/+/360414 Trust: Roland Shoemaker <roland@golang.org> Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Roland Shoemaker <roland@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-01 20:57:34 +03:00
case "vulndb", "vuln":
// vulndb currently uses a dependency which does not build cleanly
// on aix-ppc64. Until that issue is resolved, skip vulndb on
// this builder.
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// (https://go.dev/issue/49218).
dashboard: skip vulndb on aix-ppc64 vulndb currently uses a dependency which does not build cleanly on this os/arch combo. Until that issue is resolved, skip (this code is not intended to be run on a large variety of systems, so it should be fine for the foreseeable future.) Fixes golang/go#49218 Change-Id: I174daf963dbb4493141330bae55398e9f97f0fc1 Reviewed-on: https://go-review.googlesource.com/c/build/+/360414 Trust: Roland Shoemaker <roland@golang.org> Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Roland Shoemaker <roland@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-01 20:57:34 +03:00
return false
dashboard: don't build x/net master against Go 1.12 on aix Per request in https://golang.org/issue/31564#issuecomment-484786144 Change-Id: I52e496083b84aa021e7d7cdcda19c96980e1518f Reviewed-on: https://go-review.googlesource.com/c/build/+/172878 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-19 17:37:11 +03:00
}
dashboard, cmd/release: remove what's unused as of Go 1.16 release We can drop the 32-bit and 10.11 macOS builders, they're unused. Remove FreeBSD 11.1 builder, it's unused. Update freebsd-amd64-race to use the latest available FreeBSD builder. Simplify build policy and comments, removing anything that mentioned Go version 1.14 or older, since they're not relevant anymore. Drop Go 1.14 support from minSupportedMacOSVersion, and add support for the future Go 1.17 release, which will increase minimum macOS version requirement to macOS 10.13. Fixes golang/go#40562. Change-Id: I7beeec0952a516afe99a5154b22c7f25ceeb3da1 Reviewed-on: https://go-review.googlesource.com/c/build/+/293771 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-02-19 20:17:28 +03:00
return buildRepoByDefault(repo)
dashboard: don't build x/net master against Go 1.12 on aix Per request in https://golang.org/issue/31564#issuecomment-484786144 Change-Id: I52e496083b84aa021e7d7cdcda19c96980e1518f Reviewed-on: https://go-review.googlesource.com/c/build/+/172878 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-19 17:37:11 +03:00
},
dashboard: add aix-ppc64 builder This is a starting point for adding an aix-ppc64 reverse builder. There can be further adjustments made to it as needed. Updates golang/go#27160. Change-Id: I8a61adbe21f1a08265df9a206d94bb04e880a508 Reviewed-on: https://go-review.googlesource.com/131335 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-08-24 21:41:05 +03:00
})
dashboard: add new linux-amd64-wsl builder Updates golang/go#17365 Change-Id: I90b9c1c8f82ae9164deacea36ff5dafd008eef03 Reviewed-on: https://go-review.googlesource.com/c/build/+/272266 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-24 19:44:38 +03:00
addBuilder(BuildConfig{
cmd/coordinator,dashboard: add privateGoProxy setting Builders behind firewall may not access to proxy.golang.org but has its own private Go module proxy linux-mips64le-mengzhuo linux-amd64-wsl linux-riscv64-unmatched NeedsGoProxy is for long test used which we should not change. Update golang/go#42971 Change-Id: If300b751487ae08e05f5200581eb4c2719706a56 Reviewed-on: https://go-review.googlesource.com/c/build/+/275412 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Lee Baokun <bk@golangcn.org> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-04-28 17:24:01 +03:00
Name: "linux-amd64-wsl",
HostType: "host-linux-amd64-wsl",
Notes: "Windows 10 WSL2 Ubuntu",
FlakyNet: true,
SkipSnapshot: true, // The builder has a slow uplink bandwidth.
privateGoProxy: true, // this builder is behind firewall
dashboard: add new linux-amd64-wsl builder Updates golang/go#17365 Change-Id: I90b9c1c8f82ae9164deacea36ff5dafd008eef03 Reviewed-on: https://go-review.googlesource.com/c/build/+/272266 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-11-24 19:44:38 +03:00
})
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
addBuilder(BuildConfig{
dashboard: SkipSnapshot for linux-amd64-perf Since this builder doesn't build the go repo, it will be waiting forever for a snapshot. Instead, just build Go for each run. For golang/go#49207 Change-Id: I34a73b507278db402c478b4f5956633996772aae Reviewed-on: https://go-review.googlesource.com/c/build/+/361754 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-05 22:01:27 +03:00
Name: "linux-amd64-perf",
HostType: "host-linux-amd64-perf",
Notes: "Performance testing for linux-amd64",
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
buildsRepo: func(repo, branch, goBranch string) bool {
dashboard: add linux-amd64-perf builder for x/tools Note that this will be initially failing, as x/benchmarks/cmd/bench doesn't yet support x/tools. Unfortunately we can't set a KnownIssue for just one subrepo. For golang/go#53538. Change-Id: I99e83e35162685de5b490bcfb788a20f2cc4646d Reviewed-on: https://go-review.googlesource.com/c/build/+/442615 Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Michael Pratt <mpratt@google.com>
2022-10-12 23:20:35 +03:00
if repo == "benchmarks" {
// Benchmark the main Go repo.
return true
}
if repo == "tools" {
// Benchmark x/tools.
//
// When benchmarking subrepos, we ignore the Go
// commit and always use the most recent Go
// release, meaning we get identical duplicate
// runs for each Go commit that runs at the
// same subrepo commit.
//
// Limit to running on release branches since
// they have far fewer Go commits than tip,
// thus reducing the the number of duplicate
// runs.
return strings.HasPrefix(goBranch, "release-branch.")
}
return false
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
},
dashboard: SkipSnapshot for linux-amd64-perf Since this builder doesn't build the go repo, it will be waiting forever for a snapshot. Instead, just build Go for each run. For golang/go#49207 Change-Id: I34a73b507278db402c478b4f5956633996772aae Reviewed-on: https://go-review.googlesource.com/c/build/+/361754 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-05 22:01:27 +03:00
RunBench: true,
SkipSnapshot: true,
dashboard/builders: add KI on linux-amd64-perf The perf builder is broken on the tools repo. Add a KI for it. Updates golang/go#53538. Change-Id: I31873ac336a7fe681a2e1356768fd011ebcfe2b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/449036 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com>
2022-11-09 21:23:26 +03:00
KnownIssues: []int{53538},
dashboard: add linux-amd64-perf host and builder Add a new builder to run the x/benchmarks performance tests on linux-amd64. For now, this runs on a GCE C2 instance type, as these instances have well-defined, consistent CPUs and other server architecture components. In basic noise testing, even standard VMs of this type appear to be fairly low noise. As we gain experience with actual monitoring, we may change this to a sole-tenant VM type or even a dedicated machine if necessary. For golang/go#49207 Change-Id: I17eaeeb5349af925249940bebd5b860a2579e6df Reviewed-on: https://go-review.googlesource.com/c/build/+/354311 Trust: Michael Pratt <mpratt@google.com> Run-TryBot: Michael Pratt <mpratt@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2021-10-01 21:59:33 +03:00
})
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
}
dashboard: add s390x cross-compile-only builder and release config Also modifies cmd/release to wire it up. Updates golang/go#16443 Change-Id: Ie80a224957f6f662d0aec0fd083e2a57e30436c4 Reviewed-on: https://go-review.googlesource.com/28172 Reviewed-by: Jessica Frazelle <me@jessfraz.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2016-08-30 23:32:33 +03:00
dashboard, cmd/coordinator: support multiple builder owners Prefer displaying GitHub usernames for convenience of pinging in GitHub issues, since all current builder owners have them. Keep it possible to use an email or something else if no GitHub account exists. Update the owner of the Corellium builders to be individual GitHub account, so that it can be pinged in an issue. The GitHub organization is already mentioned in the builder notes. Also switch to html/template (instead of text/template) for rendering the builders page. Fixes golang/go#49596. Change-Id: I89a96eb8f7a3057bc1f3aaee16abc9c776c45ee7 Reviewed-on: https://go-review.googlesource.com/c/build/+/363983 Trust: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2021-11-16 20:42:29 +03:00
// addBuilder adds c to the Builders map after doing some checks.
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
func addBuilder(c BuildConfig) {
if c.Name == "" {
panic("empty name")
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
if c.HostType == "" {
panic(fmt.Sprintf("missing HostType for builder %q", c.Name))
}
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
if _, dup := Builders[c.Name]; dup {
dashboard: convert plan9-arm, plan9-amd64-9front, nacl-arm to buildlets Updates golang/go#21191 Change-Id: I577dad51d490d7e281ccde9fa7d82bb1bee95bd9 Reviewed-on: https://go-review.googlesource.com/53417 Reviewed-by: David du Colombier <0intro@gmail.com>
2017-08-06 18:57:06 +03:00
panic("dup name " + c.Name)
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
}
dashboard: add IsGoogle We assume builders run by Google are reliable and secure. Add the concept directly to the host config. For golang/go#48523. Change-Id: I43288ca25e1c6e1915645b77c09eeb3a0609be7e Reviewed-on: https://go-review.googlesource.com/c/build/+/435499 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
2022-10-04 23:42:12 +03:00
if c.HostConfig().GoogleReverse && !c.IsReverse() {
panic("GoogleReverse is set but the builder isn't reverse")
}
all: split builder config into builder & host configs Our builders are named of the form "GOOS-GOARCH" or "GOOS-GOARCH-suffix". Over time we've grown many builders. This CL doesn't change that. Builders continue to be named and operate as before. Previously the build configuration file (dashboard/builders.go) made each builder type ("linux-amd64-race", etc) define how to create a host running a buildlet of that type, even though many builders had identical host configs. For example, these builders all share the same host type (a Kubernetes container): linux-amd64 linux-amd64-race linux-386 linux-386-387 And these are the same host type (a GCE VM): windows-amd64-gce windows-amd64-race windows-386-gce This CL creates a new concept of a "hostType" which defines how the buildlet is created (Kube, GCE, Reverse, and how), and then each builder itself references a host type. Users never see the hostType. (except perhaps in gomote list output) But they at least never need to care about them. Reverse buildlets now can only be one hostType at a time, which simplifies things. We were no longer using multiple roles per machine once moving to VMs for OS X. gomote continues to operate as it did previously but its underlying protocol changed and clients will need to be updated. As a new feature, gomote now has a new flag to let you reuse a buildlet host connection for different builder rules if they share the same underlying host type. But users can ignore that. This CL is a long-standing TODO (previously attempted and aborted) and will make many things easier and faster, including the linux-arm cross-compilation effort, and keeping pre-warmed buildlets of VM types ready to go. Updates golang/go#17104 Change-Id: Iad8387f48680424a8441e878a2f4762bf79ea4d2 Reviewed-on: https://go-review.googlesource.com/29551 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
2016-09-22 00:27:37 +03:00
if _, ok := Hosts[c.HostType]; !ok {
panic(fmt.Sprintf("undefined HostType %q for builder %q", c.HostType, c.Name))
cmd/coordinator: start of a Kubernetes buildlet pool Updates golang/go#12546 Change-Id: Ia70baeb1df441509f70c77e7b94e7eb9fddccbf3 Reviewed-on: https://go-review.googlesource.com/14392 Reviewed-by: Evan Brown <evanbrown@google.com>
2015-09-09 01:18:47 +03:00
}
dashboard, cmd/coordinator: clean up snapshot code, add snapshot opt-out The snapshot code had an old workaround that's no longer relevant. Remove it. Also, add a BuildConfig.SkipSnapshot bool, and use it for the slow mips builders. Fixes golang/go#19953 Change-Id: I114bb0a524184eaaae5be4715ce63f6adc519c2e Reviewed-on: https://go-review.googlesource.com/40505 Reviewed-by: Sarah Adams <shadams@google.com>
2017-04-13 07:34:42 +03:00
if c.SkipSnapshot && (c.numTestHelpers > 0 || c.numTryTestHelpers > 0) {
panic(fmt.Sprintf("config %q's SkipSnapshot is not compatible with sharded test helpers", c.Name))
}
dashboard: allow multiple known-issues for builders We may know of more than one issue affecting a builder. In some contexts (such as the build dashboard) we only have enough room to display one of those, but in other contexts (such as SlowBot failure messages) it may be useful to see all of them as a list. Moreover, this way we don't have to remember to check for other known issues when removing an issue that has been resolved. For golang/go#52653. Change-Id: I9da42a3bf99ad24ec4b3ba9c4e6ce214b9f9cac7 Reviewed-on: https://go-review.googlesource.com/c/build/+/408696 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-05-26 18:06:10 +03:00
for i, issue := range c.KnownIssues {
if issue == 0 {
panic(fmt.Errorf("config %q's KnownIssues slice has a zero issue at index %d", c.Name, i))
}
}
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
types := 0
all: rename Kube to Container and IsGCE to IsVM Once containers run on COS instead of Kubernetes, one name (Kube*) is wrong and the other (GCE) is ambiguous. So rename them now to be more specific. No behavior changes. Just renaming in this step, to reduce size of next CL. Updates golang/go#25108 Change-Id: Ib09eb682ef74acbbf6ed50b46074f834ef5e0c0b Reviewed-on: https://go-review.googlesource.com/111639 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2018-05-05 19:36:05 +03:00
for _, fn := range []func() bool{c.IsReverse, c.IsContainer, c.IsVM} {
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
if fn() {
types++
}
}
if types != 1 {
all: use Container-Optimized VMs instead of Kubernetes for buildlet containers Fixes golang/go#25108 Change-Id: I084669b52b699700ed26a7fdd890d9205a8b9dc9 Reviewed-on: https://go-review.googlesource.com/111267 Reviewed-by: Andrew Bonventre <andybons@golang.org>
2018-05-04 05:42:17 +03:00
panic(fmt.Sprintf("build config %q host type inconsistent (must be Reverse, Image, or VM)", c.Name))
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
}
all: change dashboard.BuildConfig to be a pointer type, like HostConfig BuildConfig grew way too large and has too many slices & such to be a value type. Make it a pointer type, which matches HostConfig. Change-Id: Ie625bece9d6d8c1ec6cff26e77416bd9b1f256d8 Reviewed-on: https://go-review.googlesource.com/c/145077 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 20:52:25 +03:00
Builders[c.Name] = &c
dashboard: move builder configuration out of coordinator into a package The new package will be used by the buildlet command line tool in the future. Also use the metadata package in the coordinator for the master build key, since it was already depending on that package. Might as well use it. Change-Id: I6ad7593787ebba364090951ccbaecb4aa38e1dd6 Reviewed-on: https://go-review.googlesource.com/2920 Reviewed-by: Andrew Gerrand <adg@golang.org>
2015-01-15 23:46:22 +03:00
}
all: misc cleanup, docs, actually add Alpine builder -- move policy of which builders are trybots out of coordinator and into dashboard/builders.go. -- move some GCE-specific code from coordinator.go to gce.go. -- rename an old "watcher" reference to "gitmirror" -- add some docs -- actually add the Alpine builder, missing from https://golang.org/cl/33890 Fixes golang/go#17891 Change-Id: Ia63671ca09aec322ed57b3663e0ac5042cdc56f2 Reviewed-on: https://go-review.googlesource.com/40395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-12 03:35:37 +03:00
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
// tryNewMiscCompile is an intermediate step towards adding a real addMiscCompile TryBot.
// It adds a post-submit-only builder with KnownIssue, GoDeps set to the provided values,
// and runs on a limited set of branches to get test results without potential disruption
// for contributors. It can be modified as needed when onboarding a misc-compile builder.
func tryNewMiscCompile(suffix, rx string, knownIssue int, goDeps []string) {
if knownIssue == 0 {
panic("tryNewMiscCompile: knownIssue parameter must be non-zero")
}
addBuilder(BuildConfig{
Name: "misc-compile" + suffix,
dashboard: rename hosts to use consistent host-GOOS-GOARCH[-suffix] names This makes the table easier to understand and read quickly. It will also enable other simplifications in future CLs. Change-Id: I3060bcccbcc94951694fc8003952366474265099 Reviewed-on: https://go-review.googlesource.com/c/build/+/419983 Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: David Chase <drchase@google.com>
2022-07-26 18:46:45 +03:00
HostType: "host-linux-amd64-bullseye",
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
buildsRepo: func(repo, branch, goBranch string) bool { return repo == "go" && branch == "master" },
dashboard: allow multiple known-issues for builders We may know of more than one issue affecting a builder. In some contexts (such as the build dashboard) we only have enough room to display one of those, but in other contexts (such as SlowBot failure messages) it may be useful to see all of them as a list. Moreover, this way we don't have to remember to check for other known issues when removing an issue that has been resolved. For golang/go#52653. Change-Id: I9da42a3bf99ad24ec4b3ba9c4e6ce214b9f9cac7 Reviewed-on: https://go-review.googlesource.com/c/build/+/408696 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-05-26 18:06:10 +03:00
KnownIssues: []int{knownIssue},
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
GoDeps: goDeps,
env: []string{"GO_DISABLE_OUTBOUND_NETWORK=1"},
CompileOnly: true,
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
Notes: fmt.Sprintf("Tries buildall.bash to cross-compile & vet std+cmd packages for "+rx+", but doesn't run any tests. See go.dev/issue/%d.", knownIssue),
dashboard: promote misc-compile-darwinarm64 builder to a TryBot Testing shows that misc-compile-darwinarm64 is working as expected on recent commits. Promote it to a normal misc-compile TryBot now, with the exception that it needs to run on Go 1.16 and newer only. Fixes golang/go#42341. Change-Id: Ib4de19a2ff904fb9de056db5076ac63690eb934c Reviewed-on: https://go-review.googlesource.com/c/build/+/267123 Trust: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
2020-11-03 06:25:51 +03:00
allScriptArgs: []string{
// Filtering pattern to buildall.bash:
rx,
},
})
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// fasterTrybots is a distTestAdjust policy function.
// It skips (returns false) the test/ directory and reboot tests for trybots.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func fasterTrybots(run bool, distTest string, isNormalTry bool) bool {
if isNormalTry {
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
if strings.HasPrefix(distTest, "test:") || distTest == "reboot" {
builders: skip the reboot test in more places, especially on slower builders It's not important to run the new "reboot" bootstrapping test on all builders; a few is fine. Skip it on plan9-arm, etc, and on trybots that aren't super widely sharded. Change-Id: I35d5408eb5e034f42df5976f2b9b7f7d478d580a Reviewed-on: https://go-review.googlesource.com/c/build/+/167998 Reviewed-by: David du Colombier <0intro@gmail.com>
2019-03-18 01:28:15 +03:00
return false // skip test
}
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// noTestDirAndNoReboot is a distTestAdjust policy function.
// It skips (returns false) the test/ directory and reboot tests for all builds.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func noTestDirAndNoReboot(run bool, distTest string, isNormalTry bool) bool {
builders: skip the reboot test in more places, especially on slower builders It's not important to run the new "reboot" bootstrapping test on all builders; a few is fine. Skip it on plan9-arm, etc, and on trybots that aren't super widely sharded. Change-Id: I35d5408eb5e034f42df5976f2b9b7f7d478d580a Reviewed-on: https://go-review.googlesource.com/c/build/+/167998 Reviewed-by: David du Colombier <0intro@gmail.com>
2019-03-18 01:28:15 +03:00
if strings.HasPrefix(distTest, "test:") || distTest == "reboot" {
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
return false // skip test
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
cmd/coordinator, dashboard: add mac race builder, skip redundant trybot tests This adds a darwin-amd64-race builder. Of the four platforms that support the race detector, this was the only one missing a builder. To make up for the extra work, skip some redundant tests that the Mac (and other) builds do. The test directory is really slow, and doesn't have platform-specific code. We have amd64 & 386 test coverage for that directory via the Linux builders, which is fine. No need to do it on some of the heavier VM builders, or for trybots. Fixes golang/go#17674 Change-Id: I888119b3fdd28884b87a59d78746ab1fef6960c7 Reviewed-on: https://go-review.googlesource.com/82395 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-12-07 03:40:40 +03:00
}
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// ppc64DistTestPolicy is a distTestAdjust policy function
all: add linux-ppc64le-power10-osu builder This builder requires a patched bootstrap toolchain to accept GOPPC64=power10. Likewise, this folds in a change to update the container images to ubuntu 20.04. This is and has been running on the existing ppc64le builders for a couple months already. Change-Id: Ia86cb711c99c0d8ab5f9de0ae50129fe11e6ccab Reviewed-on: https://go-review.googlesource.com/c/build/+/454515 Run-TryBot: Paul Murphy <murp@ibm.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Pratt <mpratt@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Carlos Amedee <carlos@golang.org>
2022-12-01 01:50:25 +03:00
// that's shared by linux-ppc64le, -ppc64le-power{9,10}-osu, and -ppc64.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func ppc64DistTestPolicy(run bool, distTest string, isNormalTry bool) bool {
dashboard: skip reboot test on ppc64x builders Updates golang/go#35233 Change-Id: Icfa19da5d0dd3c47ffa94d11f069b8836c86cdcc Reviewed-on: https://go-review.googlesource.com/c/build/+/204038 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 18:02:19 +03:00
if distTest == "reboot" {
// Skip test. It seems to use a lot of memory?
dashboard: remove stale machineType entries from builders CL 413420 changed the default GCE instance type from e2-highcpu-2 (2 vCPU, 2 GB) to e2-standard-8 (8 vCPU, 32 GB), and the default containerized instance type from e2-standard-4 (4 vCPU, 16 GB) to e2-standard-16 (16 vCPU, 64 GB). Any entries in the dashboard table that previously opted in to bigger, faster machines are now opting into smaller, slower machines. That seems undesirable, so delete all the opt-in smaller, slower machineType entries. For golang/go#17104. Change-Id: I88806c1586b219257229c9e2302464efdcc558a6 Reviewed-on: https://go-review.googlesource.com/c/build/+/419077 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Carlos Amedee <carlos@golang.org> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
2022-07-22 19:04:15 +03:00
// See https://go.dev/issue/35233.
dashboard: skip reboot test on ppc64x builders Updates golang/go#35233 Change-Id: Icfa19da5d0dd3c47ffa94d11f069b8836c86cdcc Reviewed-on: https://go-review.googlesource.com/c/build/+/204038 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 18:02:19 +03:00
return false
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: skip reboot test on ppc64x builders Updates golang/go#35233 Change-Id: Icfa19da5d0dd3c47ffa94d11f069b8836c86cdcc Reviewed-on: https://go-review.googlesource.com/c/build/+/204038 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 18:02:19 +03:00
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
// mipsDistTestPolicy is a distTestAdjust policy function
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
// that's shared by the slow mips builders.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func mipsDistTestPolicy(run bool, distTest string, isNormalTry bool) bool {
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
switch distTest {
case "api", "reboot":
return false
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: add MIPS builders at RT-RK Updates golang/go#31217 Change-Id: I3c947fa1dcd0f1d938ffa4dfe565a35b2ccc3533 Reviewed-on: https://go-review.googlesource.com/c/build/+/204043 Reviewed-by: Bryan C. Mills <bcmills@google.com>
2019-10-29 23:35:07 +03:00
}
// mipsBuildsRepoPolicy is a buildsRepo policy function
// that's shared by the slow mips builders.
func mipsBuildsRepoPolicy(repo, branch, goBranch string) bool {
switch repo {
case "go", "net", "sys":
return branch == "master" && goBranch == "master"
default:
return false
}
}
dashboard: disable api/reboot test for unmatched It takes >15m to complete api and reboot tests for Hifive unmatched which we don't need. Change-Id: Ie4535264d2e8ef4496c54fb5f412d5ec773f538a Reviewed-on: https://go-review.googlesource.com/c/build/+/346709 Trust: Meng Zhuo <mzh@golangcn.org> Run-TryBot: Meng Zhuo <mzh@golangcn.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
2021-09-01 10:08:03 +03:00
// riscvDistTestPolicy is same as mipsDistTestPolicy for now.
var riscvDistTestPolicy = mipsDistTestPolicy
dashboard: add linux-loong64-3a5000 builder Updates golang/go#46229 Change-Id: Ib48e1e64d96a07d5c5282d78935124faf75c89d7 Reviewed-on: https://go-review.googlesource.com/c/build/+/347309 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Trust: Cherry Mui <cherryyz@google.com>
2021-09-02 10:51:28 +03:00
// loong64DistTestPolicy is a distTestAdjust policy function
func loong64DistTestPolicy(run bool, distTest string, isNormalTry bool) bool {
switch distTest {
case "api", "reboot":
return false
}
return run
}
// loong64BuildsRepoPolicy is a buildsRepo policy function
func loong64BuildsRepoPolicy(repo, branch, goBranch string) bool {
switch repo {
case "go", "net", "sys":
return branch == "master" && goBranch == "master"
default:
return false
}
}
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
// TryBuildersForProject returns the builders that should run as part of
// a TryBot set for the given project.
// The project argument is of the form "go", "net", "sys", etc.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// The branch is the branch of that project ("master", "release-branch.go1.12", etc)
// The goBranch is the branch of Go to use. If proj == "go", then branch == goBranch.
func TryBuildersForProject(proj, branch, goBranch string) []*BuildConfig {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
return buildersForProject(proj, branch, goBranch, (*BuildConfig).BuildsRepoTryBot)
}
// isBuilderFunc is the type of functions that report whether a builder
// should be run given a project, branch and goBranch.
type isBuilderFunc func(conf *BuildConfig, proj, branch, goBranch string) bool
dashboard: minor comment fixes These were responses to comments in a prior CL that I neglected to mail. Change-Id: I9a68fe743ad8cb39860250da0fc2f06215270880 Reviewed-on: https://go-review.googlesource.com/c/build/+/377454 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-10 22:19:02 +03:00
// buildersForProject returns the builders that should be run for the given project,
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
// using isBuilder to test each builder.
// See TryBuildersForProject for the valid forms of proj, branch and goBranch.
func buildersForProject(proj, branch, goBranch string, isBuilder isBuilderFunc) []*BuildConfig {
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
var confs []*BuildConfig
for _, conf := range Builders {
dashboard: build x/vulndb only on linux-amd64 The vulndb repo is not intended for external use. It consists of some binaries and servers used by the Go team for vulnerability work. So there is no need for it to build on a variety of systems and Go versions. In fact, it only needs to work on the current version of Go on vanilla Linux. Fixes golang/go#50472 Change-Id: I37bc0136ad92f2b959ff8ef4e89c3bde3a2d31d6 Reviewed-on: https://go-review.googlesource.com/c/build/+/375957 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2022-01-07 23:29:05 +03:00
if isBuilder(conf, proj, branch, goBranch) {
dashboard, cmd/coordinator: move more config out of coordinator into dashboard And with the increased flexibility, enable trybots for more repos for the "sys" project. Details: https://github.com/golang/go/issues/24893#issuecomment-433517519 Fixes golang/go#24893 Change-Id: I89ce6f219be986201332f8fad11c774bdd6246da Reviewed-on: https://go-review.googlesource.com/c/145157 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2018-10-26 22:21:58 +03:00
confs = append(confs, conf)
}
}
sort.Slice(confs, func(i, j int) bool {
return confs[i].Name < confs[j].Name
})
return confs
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
dashboard: treat dev branches as current If a dev branch is active, it will be current. If it is not active, it is probably not current, but we don't build on the branch so it doesn't matter anyway. Specifically, the dev.link branch is currently under active development, and it would be good to have a large set of builders run on the branch to catch problems. (E.g., AIX build was broken but not noticed.) Fixes golang/go#37953. Change-Id: Idd7e3edaaff1b4d2cee17da552a96df2b00716e9 Reviewed-on: https://go-review.googlesource.com/c/build/+/223381 Run-TryBot: Cherry Zhang <cherryyz@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-03-14 00:09:21 +03:00
// atLeastGo1 reports whether branch is "release-branch.go1.N" where N >= min.
// It assumes "master" and "dev.*" branches are already greater than min, and
// always includes them.
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
func atLeastGo1(branch string, min int) bool {
if branch == "master" {
return true
}
dashboard: treat dev branches as current If a dev branch is active, it will be current. If it is not active, it is probably not current, but we don't build on the branch so it doesn't matter anyway. Specifically, the dev.link branch is currently under active development, and it would be good to have a large set of builders run on the branch to catch problems. (E.g., AIX build was broken but not noticed.) Fixes golang/go#37953. Change-Id: Idd7e3edaaff1b4d2cee17da552a96df2b00716e9 Reviewed-on: https://go-review.googlesource.com/c/build/+/223381 Run-TryBot: Cherry Zhang <cherryyz@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2020-03-14 00:09:21 +03:00
if strings.HasPrefix(branch, "dev.") {
// Treat dev branches current.
// If a dev branch is active, it will be current.
// If it is not active, it doesn't matter anyway.
// TODO: dev.boringcrypto.go1.N branches may be the
// exception. Currently we only build boringcrypto
// on linux/amd64 and windows/386, which support all
// versions of Go, so it doesn't actually matter.
return true
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
major, minor, ok := version.ParseReleaseBranch(branch)
return ok && major == 1 && minor >= min
}
dashboard: disable darwin-amd64-10_11 builder on Go 1.15+ Go 1.15 will require macOS 10.12 and newer¹, so keep the OS X 10.11 builder enabled only on release branches for 1.14 and older. ¹ https://golang.org/doc/go1.14#darwin Fixes golang/go#37425 Change-Id: I89ab0eb56729fe16fb3a524c8f7b9bb25751d708 Reviewed-on: https://go-review.googlesource.com/c/build/+/222797 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
2020-03-10 20:26:20 +03:00
// atMostGo1 reports whether branch is "release-branch.go1.N" where N <= max.
// It assumes "master" branch is already greater than max, and doesn't include it.
func atMostGo1(branch string, max int) bool {
major, minor, ok := version.ParseReleaseBranch(branch)
return ok && major == 1 && minor <= max
}
dashboard: unify post-submit & trybot policy in builders.go, not coordinator This removes a bunch of TODOs about scattered policy and moves it all into builders.go. While here, * add a bunch of tests * unexport some things * rename some things * document some things * adjust FreeBSD policy as function of branch (per Go 1.12 being last to support FreeBSD 10.x, and to unblock CL 165801) * set GO_BUILDER_SET_GOPROXY=coordinator for reverse buildlets, which is necessary to remove the oauth2 & build special cases in the config * change Elias Naur's mobile builder to how I think he wants it (he was fighting the old system) * add $HOME on the Solaris smartos builder, which was missing & causing tests to fail lately * make the (currently failing) longtest builder have GOPROXY set * remove an allocation in version.ParseReleaseBranch Fixes golang/go#9603 Updates golang/go#14594 Change-Id: I50a23ad7cdf478c95b14bee9b3931ba361baacfa Reviewed-on: https://go-review.googlesource.com/c/build/+/166218 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-07 20:44:41 +03:00
// onlyGo is a common buildsRepo policy value that only builds the main "go" repo.
func onlyGo(repo, branch, goBranch string) bool { return repo == "go" }
all: add a macOS 10.14 (Mojave) builder Fixes golang/go#27806 Change-Id: I576f563acb2c50cd0456cd4e6a1271b9aa59c9df Reviewed-on: https://go-review.googlesource.com/c/build/+/169498 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-27 02:04:31 +03:00
dashboard: don't build x/exp and x/mobile on the plan9 builders Updates golang/go#11811 Change-Id: I776652a3b980772f34d65d8c245a143814aadb6a Reviewed-on: https://go-review.googlesource.com/c/build/+/209338 Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2019-11-28 13:33:00 +03:00
// onlyMasterDefault is a common buildsRepo policy value that only builds
// default repos on the master branch.
func onlyMasterDefault(repo, branch, goBranch string) bool {
dashboard: document and clarify defaultBuildsRepoPolicy The defaultBuildsRepoPolicy function was very important in that any changes to it would affect many builders, but it was not documented well. This refactor attempts to improve the situation. It turned out better to also rename defaultBuildsRepoPolicy to buildRepoByDefault and limit its scope to report whether a given repo should be built by default. The branch and goBranch parameters were never used, and thus misleading. If they're needed in the future, we can easily re-add them. The name defaultBuildsRepoPolicy made it sound as if it was the entire "builds repo" policy, bun reality most of the policy is implemented in the BuildConfig.buildsRepoAtAll method and is non-configurable. Only a small part of the policy was in defaultBuildsRepoPolicy. For golang/go#39156. Change-Id: Ie7c6a68bd624056362dc7d964bd8d640f665b35a Reviewed-on: https://go-review.googlesource.com/c/build/+/240687 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-07-01 21:45:10 +03:00
return branch == "master" && goBranch == "master" && buildRepoByDefault(repo)
dashboard, cmd/coordinator: remove Joyent builders Joyent.com is shutting down their public cloud, so we no longer have our GOOS=solaris or GOOS=illumos builders there. Maybe somebody will find a new place to run them. Or maybe the ports will be abandoned. We'll see. Updates golang/go#15581 Change-Id: I0590227ce61b6b298b6aa4554e5e3bc9e4c464b5 Reviewed-on: https://go-review.googlesource.com/c/build/+/200219 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-10-10 07:17:45 +03:00
}
dashboard: only test plan9 at master The plan9 port doesn't need to be tested against older Go releases. Its userbase runs at master. Change-Id: I710d98560b234c7555c7be526aa2efdb6473c439 Reviewed-on: https://go-review.googlesource.com/c/build/+/170519 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-04-03 08:03:37 +03:00
dashboard: omit the website repo on plan9 The plan9 builders have relatively slow filesystems, and the website repo is relatively filesystem-intensive — many of its tests walk and process large trees of website content. Instead of trying to precisely tune the x/website tests to pass on the plan9 builders, let's skip this repo on them. For golang/go#49338. Change-Id: Ieaf50fb6955a6b39012a23ff72e61c1c31e4ce7c Reviewed-on: https://go-review.googlesource.com/c/build/+/362975 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-10 19:28:50 +03:00
// plan9Default is like onlyMasterDefault, but also omits repos that are
// both filesystem-intensive and unlikely to be relevant to plan9 users.
func plan9Default(repo, branch, goBranch string) bool {
switch repo {
dashboard: skip x/review on plan9 builders Plan 9 has a non-standard "git" CLI, and x/review contains only a git hook. Change-Id: I9b77ae772afa714e95d814b038a4ebedbd95151c Reviewed-on: https://go-review.googlesource.com/c/build/+/368154 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: David du Colombier <0intro@gmail.com>
2021-12-01 18:23:06 +03:00
case "review":
// The x/review repo tests a Git hook, but the plan9 "git" doesn't have the
// same command-line API as "git" everywhere else.
return false
dashboard: omit the website repo on plan9 The plan9 builders have relatively slow filesystems, and the website repo is relatively filesystem-intensive — many of its tests walk and process large trees of website content. Instead of trying to precisely tune the x/website tests to pass on the plan9 builders, let's skip this repo on them. For golang/go#49338. Change-Id: Ieaf50fb6955a6b39012a23ff72e61c1c31e4ce7c Reviewed-on: https://go-review.googlesource.com/c/build/+/362975 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-10 19:28:50 +03:00
case "website":
// The x/website tests read and check the website code snippets,
// which require many filesystem walk and read operations.
return false
dashboard: exclude x/vuln and x/vulndb from Plan 9 builders The vulncheck package and govulncheck command understand common binary formats, but not Plan 9's. Fixes golang/go#52219. Change-Id: Ia3fb6012d58c01af115a83dc4b74e60847a20c03 Reviewed-on: https://go-review.googlesource.com/c/build/+/398934 Trust: Jonathan Amsterdam <jba@google.com> Run-TryBot: Jonathan Amsterdam <jba@google.com> Trust: Bryan Mills <bcmills@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org>
2022-04-07 22:19:55 +03:00
case "vulndb", "vuln":
// vulncheck can't read plan9 binaries.
return false
dashboard: omit the website repo on plan9 The plan9 builders have relatively slow filesystems, and the website repo is relatively filesystem-intensive — many of its tests walk and process large trees of website content. Instead of trying to precisely tune the x/website tests to pass on the plan9 builders, let's skip this repo on them. For golang/go#49338. Change-Id: Ieaf50fb6955a6b39012a23ff72e61c1c31e4ce7c Reviewed-on: https://go-review.googlesource.com/c/build/+/362975 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2021-11-10 19:28:50 +03:00
default:
return onlyMasterDefault(repo, branch, goBranch)
}
}
all: add a macOS 10.14 (Mojave) builder Fixes golang/go#27806 Change-Id: I576f563acb2c50cd0456cd4e6a1271b9aa59c9df Reviewed-on: https://go-review.googlesource.com/c/build/+/169498 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-27 02:04:31 +03:00
// disabledBuilder is a buildsRepo policy function that always return false.
func disabledBuilder(repo, branch, goBranch string) bool { return false }
dashboard: skip some slow tests on Macs We have limited Mac resources. It's not worth wasting time testing portable things on them. Change-Id: Iaaa1d02582da7f8435217fbb32dcb7235c560a41 Reviewed-on: https://go-review.googlesource.com/c/build/+/169681 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-28 02:03:50 +03:00
// macTestPolicy is the test policy for Macs.
//
// We have limited Mac resources. It's not worth wasting time testing
// portable things on them. That is, if there's a slow test that will
// still fail slowly on another builder where we have more resources
// (like linux-amd64), then there's no point testing it redundantly on
// the Macs.
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
func macTestPolicy(run bool, distTest string, isNormalTry bool) bool {
dashboard: skip some slow tests on Macs We have limited Mac resources. It's not worth wasting time testing portable things on them. Change-Id: Iaaa1d02582da7f8435217fbb32dcb7235c560a41 Reviewed-on: https://go-review.googlesource.com/c/build/+/169681 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-28 02:03:50 +03:00
if strings.HasPrefix(distTest, "test:") {
return false
}
switch distTest {
case "reboot", "api", "doc_progs",
"wiki", "bench_go1", "codewalk":
return false
}
cmd/coordinator, dashboard: don't skip cmd/dist tests for SlowBots When a user explicitly requests a SlowBot builder via the TRY= syntax, it is a signal that they're willing to wait longer for test results. It's more useful to not skip any tests and give the user confidence that the SlowBot run will catch all issues that would otherwise be caught only by post-submit builders after the CL is submitted. This is done by considering a TryBot that isn't an explicit SlowBot to be a "normal TryBot", and the ShouldRunDistTest policy function is provided a parameter specifying whether it's a normal TryBot (non-SlowBot) run. Tests are only skipped during normal TryBot runs, not SlowBot runs. Fixes golang/go#38279. For golang/go#34501. Change-Id: Ia11fd51c71f9de1089b6b6f4c027014893f224b9 Reviewed-on: https://go-review.googlesource.com/c/build/+/227779 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 23:24:30 +03:00
if isNormalTry {
dashboard: skip some slow tests on Macs We have limited Mac resources. It's not worth wasting time testing portable things on them. Change-Id: Iaaa1d02582da7f8435217fbb32dcb7235c560a41 Reviewed-on: https://go-review.googlesource.com/c/build/+/169681 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-28 02:03:50 +03:00
switch distTest {
case "runtime:cpu124", "race", "moved_goroot":
return false
}
// TODO: more. Look at bigquery results once we have more data.
}
dashboard: refactor mechanism for adjusting cmd/dist test policy Previously, the behavior of ShouldRunDistTest could be overridden by an individual builder by setting a the shouldRunDistTest field to a custom policy implementation. A pitfall of this approach is that it requires each custom policy to reimplement the default cmd/dist test policy as well. If that isn't done when attempting to make a small adjustment to the default policy, the result is that the default policy is ignored. The fasterTrybots policy, as the name suggests, exists to skip some tests in trybot mode. Due to the problem above, it was causing some builders to run more tests in trybot mode than they would if it weren't applied. For example, the freebsd-amd64-12_0 builder should have been skipping the "api" test in trybot mode, but wasn't. This refactor fixes that by modifying the approach for how individual builders can customize the cmd/dist test behavior. Now, a function distTestAdjust is called with the first parameter specifying the default policy decision. That function can adjust the decision as it sees fit, but otherwise it preserves its initial value in situations where no change is intended to be made. For golang/go#38279. Change-Id: I220248f51abfc8e77195ae0c9134a17f7cac9bc2 Reviewed-on: https://go-review.googlesource.com/c/build/+/227777 Reviewed-by: Alexander Rakoczy <alex@golang.org>
2020-04-09 19:47:03 +03:00
return run
dashboard: skip some slow tests on Macs We have limited Mac resources. It's not worth wasting time testing portable things on them. Change-Id: Iaaa1d02582da7f8435217fbb32dcb7235c560a41 Reviewed-on: https://go-review.googlesource.com/c/build/+/169681 Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
2019-03-28 02:03:50 +03:00
}