-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_listen_for_bound_device_configs failed #2860
Comments
Test passed in build fbcdef1 (https://source.cloud.google.com/results/invocations/04397697-dd91-4cfb-a092-94cdeb1e87b2)! Closing this issue. |
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_listen_for_bound_device_configs failed |
This is a known flaky test. |
Oops! Looks like this issue is still flaky. 😬 I reopened the issue, but a human will need to close it again. iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_listen_for_bound_device_configs failed |
This is a known flaky test. |
Oops! Looks like this issue is still flaky. 😬 I reopened the issue, but a human will need to close it again. buildID: a669fae |
Potentially fixed in #3068 |
Oops! Looks like this issue is still flaky. 😬 I reopened the issue, but a human will need to close it again. commit: 1037f47 |
I may need to use the "safe clear" delete for instances where the tests are interrupted. |
* [iot] fix: use fixtures for resource setup/teardown fixes #2861 fixes #3323 fixes #2859 fixes #2860 * avoid topic name conflict * refactored out the fixtures * share the fixtures within two tests * correct dependencies between fixtures * use threading for cordinating between background and foreground threads.
iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_listen_for_bound_device_configs failed
buildID: 48f7af7
buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31
status: failed
The text was updated successfully, but these errors were encountered: