You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flaky integration tests are caused by concurrency issues between three Python processes running the same test, which happens when an integration test creates a BigQuery table with a specific name without sufficient randomization (e.g. appending time.time_ns()). Importantly, appending time.time() is not sufficient; tests should use time.time_ns() and random.randint(1000, 9999).
This PR gives an example of this kind of mistake and the appropriate fix.
Expected Behavior
Ideally, all the tests should be deterministic
Current Behavior
Some tests are currently flaky which makes the development experience more painful that it could be
Steps to reproduce
Run integration tests and some of them might fail (don't know the frequency of the problem)
Specifications
Possible Solution
The text was updated successfully, but these errors were encountered: