Bigtable system test has a "race condition" if run simultaneously on same project #3333
Description
Two builds (1682 and 1683) were happening simultaneously and this caused a Bigtable system test check to fail in the second build (1683)
> self.assertEqual(len(instances), len(EXISTING_INSTANCES) + 1)
E AssertionError: 2 != 3This is because EXISTING_INSTANCES is set at module setup time while the test case is run later.
I'm not sure what a realistic fix should be?
Metadata
Metadata
Assignees
Labels
Issues related to the Bigtable API.Issues related to the Bigtable API.Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.