sessions: should get 200 failed #619
Assignees
Labels
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p1
Important issue which blocks shipping the next release. Will be fixed prior to next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
flaky-bot
bot
added
flakybot: issue
|
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (b889e24), this test passed in one build (https://console.cloud.google.com/cloud-build/builds;region=global/f23af42d-df99-4736-9c1b-e72168c21108?project=firestore-nodejs-getting-start) and failed in another build (https://console.cloud.google.com/cloud-build/builds;region=global/400bee98-14a5-483e-ac1a-3d416c45768d?project=firestore-nodejs-getting-start). |
flaky-bot
bot
added
the
flakybot: flaky
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: #482 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: b889e24
buildURL: https://console.cloud.google.com/cloud-build/builds;region=global/400bee98-14a5-483e-ac1a-3d416c45768d?project=firestore-nodejs-getting-start
status: failed
The text was updated successfully, but these errors were encountered: