Daniel Nephin 34c2d3737e build-support: remove test-flake machinery ... This machinery was not used, and does not appear to be maintained. In practice we really don't need anything to detect flaky tests. Our CI system identifies flaky tests at https://app.circleci.com/insights/github/hashicorp/consul/workflows/go-tests/tests?branch=main Mostly what we need is a way to reproduce flakes, which can be done directly with the Go CLI, using the -race, -count, and (new in Go 1.17) -shuffle flags.		2021-10-21 17:16:25 -04:00
..
build-docker.sh	Remove old UI, option to use it, and its build processes	2019-04-12 09:02:27 -06:00
build-local.sh	Quote $@ when passing around	2018-06-18 14:53:50 -04:00
envoy-library-references.sh	xds: ensure that all envoyproxy/go-control-plane protobuf symbols are linked into the final binary (#10131)	2021-04-29 14:58:26 -05:00
functions.sh	PR Updates	2018-06-19 12:47:58 -04:00
proto-gen.sh	Add failures_before_warning to checks (#10969)	2021-09-14 12:47:52 -04:00
release.sh	Allow for building pre-releases/rcs/betas	2018-06-18 17:06:38 -04:00
version.sh	Quote $@ when passing around	2018-06-18 14:53:50 -04:00