googleapis / googleapis/google-cloud-java
[java-bigtable] Allow samples tests to run concurrently
Offen
api: bigtable
priority: p3
samples
type: feature request
- Vorherrschende Sprache
- Java
- Sterne
- 2.1k
- Forks
- 1.2k
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 154
Beschreibung
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
Beitragsleitfaden
Bewertung
Dieses Issue wurde noch nicht bewertet.