-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firestore: 'test_watch_collection' systest flakes #7130
Labels
api: firestore
Issues related to the Firestore API.
flaky
testing
type: process
A process-related concern. May include testing, release, or the like.
Comments
tseaver
added
testing
api: firestore
Issues related to the Firestore API.
type: process
A process-related concern. May include testing, release, or the like.
flaky
labels
Jan 16, 2019
This was referenced Jun 24, 2019
Merged
This was referenced Jul 10, 2019
tseaver
added a commit
that referenced
this issue
Jul 10, 2019
H/t to @pchauhan-qlogic for identifying the need to unsubscribe. Also, use unique collection IDs for 'watch' tests. Exception for 'test_watch_query_order', which requires that we use the special 'users' collection, in order to take advantage of its index. Supersedes #8497. Closes #6605, #7130.
closing the issue as solved in 8638 |
PR #8638 did not address this issue: it was related to improving how the Firestore system tests clean up resources. |
Hmm, looks like I spoke too soon: changing to use a unique collection ID was part of #8638, and was likely a fix for this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: firestore
Issues related to the Firestore API.
flaky
testing
type: process
A process-related concern. May include testing, release, or the like.
Similar to #6605, #6921.
From this Kokoro Firestore run:
The text was updated successfully, but these errors were encountered: