1
0
mirror of https://github.com/golang/go synced 2024-11-06 01:46:12 -07:00
go/gopls/integration/govim
Rob Findley 0a06c69952 gopls/integration/govim: update to latest govim
Govim integration tests are now passing at govim HEAD + gopls HEAD, so
we should be able to start actively investigating any regressions on the
gopls side after this change.

Change-Id: Ibf50d7e42e19cfc80779691e2c42f643028b2e39
Reviewed-on: https://go-review.googlesource.com/c/tools/+/215897
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
2020-01-22 19:49:06 +00:00
..
cloudbuild.harness.yaml gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00
cloudbuild.yaml gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00
Dockerfile gopls/integration/govim: update to latest govim 2020-01-22 19:49:06 +00:00
README.md gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00
run_local.sh gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00
run_tests_for_cloudbuild.sh gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00

govim integration tests

Files in this directory configure Cloud Build to run govim integration tests against a gopls binary built from source.

Running on GCP

To run these integration tests in Cloud Build, use the following steps. Here we assume that $PROJECT is a valid GCP project and $BUCKET is a cloud storage bucket owned by that project.

  • cd to the root directory of the tools project.
  • (at least once per GCP project) Build the test harness:
$ gcloud builds submit \
	--project="${PROJECT}" \
	--config=gopls/integration/govim/cloudbuild.harness.yaml \
	--substitutions=_RESULT_BUCKET="${BUCKET}"
  • Run the integration tests:
$ gcloud builds submit \
	--project="${PROJECT}" \
	--config=gopls/integration/govim/cloudbuild.yaml \
	--substitutions=_RESULT_BUCKET="${BUCKET}"

Running locally

Run gopls/integration/govim/run_local.sh. This may take a while the first time it is run, as it will require building the test harness. Currently this script assumes that docker may be executed without sudo.