protobuf-go/regenerate.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 integration_test.go "$@" -regenerate
exit $?
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 20:50:52 +00: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.`

			`cd "$(git rev-parse --show-toplevel)"`
.travis.yml: fix travis CI Changes made: * Call autogen.sh before building protobuf. It's unclear how this worked before, but the README instructions for protobuf does state to run autogen.sh prior to building and installing. * Fix downloadArchive to take in a prefix path rather than the number of prefix directories to skip. The reason for this change is due to a bug in the Go build system where unexpected directories were being packed. See https://golang.org/issue/29906 * Explicitly set Travis dist to be "xenial", which comes with Go1.11. We require Go1.11 for two reasons: * The use of t.Helper in integration_test.go * Proper understanding of the -mod=vendor flag (even if all that flag does is disable modules). * Add a hack to integration_test.go to periodically output the timestamp to work around a restriction in Travis where it auto-kills the test after 10 minutes of no stdout activity. Change-Id: I114fe2855faeed091c34d79df3d97068be7eccd8 Reviewed-on: https://go-review.googlesource.com/c/164919 Reviewed-by: Herbie Ong <herbie@google.com> 2019-03-02 21:35:17 +00:00			`go test -v -mod=vendor -timeout=60m integration_test.go "$@" -regenerate`
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 20:50:52 +00:00			`exit $?`