googleapis / googleapis/google-cloud-java
[java-bigtable] Allow samples tests to run concurrently
Open
api: bigtable
priority: p3
samples
type: feature request
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 154
Description
It seems like the current samples tests hardcode their resource ids. Which makes them clobber each other when the tests are run concurrently (ie. multiple PRs are open).
We should mitigate this by either:
1. using the same strategy as the general integration tests and using timestamped resource names
2. update kokoro to take a lock for the samples tests
I would prefer 1
Contributor guide
Assessment
This issue has not been assessed yet.