protobuf-go/test.bash

#!/bin/bash
# Copyright 2018 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.

cd "$(git rev-parse --show-toplevel)"
go test -v -mod=vendor -timeout=60m -count=1 integration_test.go -failfast "$@"
exit $?
test.bash: add script for comprehensive testing This script is not currently executed by Try-Bots since they do not have the necessary infrastructure, yet. Instead, this script is intended to be ran as a pre-commit hook on each contributor's workstation. The test.bash script works on both Darwin and Linux and tests the repository across a variety of Go toolchains. The toolchains are downloaded and built into their own versioned directories and cached. Subsequent runs of the script only need to run the tests. Change-Id: Id87841ed42da422ab2e966ea073255ba866c80f7 Reviewed-on: https://go-review.googlesource.com/127826 Reviewed-by: Herbie Ong <herbie@google.com> 2018-08-03 19:13:55 -07:00			`#!/bin/bash`
			`# Copyright 2018 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.`

test.bash: rewrite the integration test in Go This CL switches the integration test to be written in Go instead of bash. The benefits are: * The logic for setting up the dependencies is more robust and handles better a situation where the dependency failed to initialize (due to network trouble, FS permission problems, etc). * The logic does a better job at cleaning up stale dependencies. For example, my .cache folder has go1.9.4, go1.9.5, go1.10.5, and go1.10.6 folders even though we don't use them anymore. * Being able to run only a subset of the integration test since you can pass "-run" to the script. * A signifcant amount of complexity in the test.bash script was running the tests in parallel. This is trivial to do in Go. The major detriment is that Go is more verbose as a "scripting" language. Change-Id: Id7e5b303fb305fdbc0368bdf809dbf29fca1d983 Reviewed-on: https://go-review.googlesource.com/c/164861 Reviewed-by: Herbie Ong <herbie@google.com> 2019-03-01 12:50:52 -08:00			`cd "$(git rev-parse --show-toplevel)"`
test.bash: add -failfast flag Rather than waiting for all tests for all Go versions to finish only to find that there was some minor breakage, fail fast so that we stop wasting time. Change-Id: Ie255ceb5ac2cbdc598a074c6da281f5e49eb1326 Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/189019 Reviewed-by: Damien Neil <dneil@google.com> 2019-08-05 14:42:21 -07:00			`go test -v -mod=vendor -timeout=60m -count=1 integration_test.go -failfast "$@"`
test.bash: rewrite the integration test in Go This CL switches the integration test to be written in Go instead of bash. The benefits are: * The logic for setting up the dependencies is more robust and handles better a situation where the dependency failed to initialize (due to network trouble, FS permission problems, etc). * The logic does a better job at cleaning up stale dependencies. For example, my .cache folder has go1.9.4, go1.9.5, go1.10.5, and go1.10.6 folders even though we don't use them anymore. * Being able to run only a subset of the integration test since you can pass "-run" to the script. * A signifcant amount of complexity in the test.bash script was running the tests in parallel. This is trivial to do in Go. The major detriment is that Go is more verbose as a "scripting" language. Change-Id: Id7e5b303fb305fdbc0368bdf809dbf29fca1d983 Reviewed-on: https://go-review.googlesource.com/c/164861 Reviewed-by: Herbie Ong <herbie@google.com> 2019-03-01 12:50:52 -08:00			`exit $?`