mirror of
https://github.com/golang/go
synced 2024-11-06 16:36:20 -07:00
046453f0ab
govim tests without a go.mod file were accidentally picking up the go.mod file from the build context at /workspace/go.mod. To fix this, run govim tests in a new, dedicated artifacts volume mounted at /artifacts. Change-Id: Ie224bbb730741d047be26a6d057a023ddc8a3453 Reviewed-on: https://go-review.googlesource.com/c/tools/+/226157 Run-TryBot: Robert Findley <rfindley@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Rebecca Stambler <rstambler@golang.org> |
||
---|---|---|
.. | ||
artifacts.go | ||
cloudbuild.harness.yaml | ||
cloudbuild.yaml | ||
Dockerfile | ||
README.md | ||
run_local.sh | ||
run_tests_for_cloudbuild.sh |
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_ID
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_ID}" \
--config=gopls/integration/govim/cloudbuild.harness.yaml
- Run the integration tests:
$ gcloud builds submit \
--project="${PROJECT_ID}" \
--config=gopls/integration/govim/cloudbuild.yaml \
--substitutions=_RESULT_BUCKET="${BUCKET}"
Fetching Artifacts
Assuming the artifacts bucket is world readable, you can fetch integration from GCS. They are located at:
- logs:
https://storage.googleapis.com/${BUCKET}/log-${EVALUATION_ID}.txt
- artifact tarball:
https://storage.googleapis.com/${BUCKET}/govim/${EVALUATION_ID}/artifacts.tar.gz
The artifacts.go
command can be used to fetch both artifacts using an
evaluation id.
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. This script
accepts two flags to modify its behavior:
--sudo: run docker with sudo
--short: run go test -short