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.

go test google.golang.org/protobuf -run='^TestIntegration$' -v -timeout=60m -count=1 "$@" -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 12:50:52 -08: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.`

all: run integration test on longtest builders in CI Remove the 'ignore' build constraint from integration_test.go and arrange things such that the integration test runs on longtest (but not longtest-race, for now anyway) builders. The existing scripts for running the invocation test locally are preserved and can be used as before. This change relies on the builders being configured to place pre-built protoc and conformance_test_runner binaries in $PATH (CL 547116); thanks to Michael for making them available via a CIPD package. Apply a few improvements to downloadFile and downloadArchive that came about from earlier prototypes that used them and uncovered some issues. Fixes golang/go#64066. Change-Id: I48b163e3ea9c441b748071da340d3e37282cc22b Co-authored-by: Michael Stapelberg <stapelberg@golang.org> Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/541123 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Michael Stapelberg <stapelberg@google.com> 2023-11-09 12:26:41 -05:00			`go test google.golang.org/protobuf -run='^TestIntegration$' -v -timeout=60m -count=1 "$@" -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 12:50:52 -08:00			`exit $?`