Avoid go test caching when running conformance tests

[glyn]

Go test caching causes the second and subsequent runs of the conformance tests
to be skipped even though changes may have been made to the system under test.

According to go help test, the idiomatic way to disable test caching
explicitly is to use -count=1.

[glyn]

/assign @bobcatfish

[glyn]

I only changed a README.

/retest

[glyn]

Thanks to @trisberg for a link to Viewing test logs. The conformance tests failed with:

route_test.go:123: The endpoint for Route pizzaplanet at domain pizzaplanet.pizzaplanet.demo-domain.com didn't serve the expected text "What a spaceport!": Get http://35.232.200.209: dial tcp 35.232.200.209:80: i/o timeout

There seems to be a problem of test flakiness, already captured in issue 879.

[adrcunha]

I only changed a README.

Currently the tests run for all changes. #815 tracks the effort to optimized that.

[adrcunha]

/retest
/lgtm
/approve

[google-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrcunha, glyn

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/OWNERS [adrcunha]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[glyn]

@adrcunha prow approved this PR an hour ago. Should I just be patient or is there some reason the merge isn't happening?

[adrcunha]

Looks like #876 is blocking tide (this is tracked by #543). You can merge it automatically if you want, no problem.

[glyn]

Thanks @adrcunha. Looks like tide is another google-internal thing I can't see yet. ;-)

@grantr Thanks for merging.