Skip to content

iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed #2861

Closed

Description

@flaky-bot

iot.api-client.mqtt_example.cloudiot_mqtt_example_test: test_gateway_send_data_for_device failed
buildID: 48f7af7
buildURL: https://source.cloud.google.com/results/invocations/067ead8d-9004-4bef-acf3-6c74265f1e31
status: failed

Activity

  1. added
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Feb 11, 2020
  2. assigned and unassigned on Feb 11, 2020
  3. flaky-bot commented on Feb 12, 2020

    @flaky-bot
    Author
  4. flaky-bot commented on Feb 26, 2020

    @flaky-bot
    Author

    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_send_data_for_device failed
    buildID: ff9682e
    buildURL: Build Status, Sponge
    status: failed

  5. 19 remaining items

  6. gguuss commented on Apr 15, 2020

    @gguuss
    Contributor

    I believe that the samples already are correctly ordering the creations and deletions. That said, the race condition, multi-threading, and being unable to delete non-empty resources are the source of pain here.

  7. tmatsuo commented on Apr 15, 2020

    @tmatsuo
    Contributor

    Yeah, if we just put 8 rpcs serially as we do in test_gateway_listen_for_bound_device_configs the success rate will be a product of those 8 rpcs (create/delete for 4 resources).

    For example, if the success rate of those rpcs are 0.9, the whole success rate will be 0.9^8 = 0.43046721. If we retry this test 5 times, the success rate will be 1 - (0.56953279^5) = 0.94007698385.

    Instead, we should have 4 fixtures with retrying each creation/deletion. If we retry 5 times for example, the success rate for each rpcs with the retries will be 1 - 0.1^5 = 0.99999, so the whole success rate will be 0.99999^8 = 0.9999200028. Without retrying the test itself, it is already more robust than the above example :)

  8. added a commit that references this issue on Apr 21, 2020
    e2cf90d
  9. flaky-bot commented on Apr 27, 2020

    @flaky-bot
    Author

    Oops! Looks like this issue is still flaky. 😬

    I reopened the issue, but a human will need to close it again.


    commit: 2b74710
    buildURL: Build Status, Sponge
    status: failed

  10. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    and removed
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    on Apr 27, 2020
  11. gguuss commented on Apr 27, 2020

    @gguuss
    Contributor

    I'm considering disabling the tests that are multithreaded as they seem to be causing issues with buildcop.

  12. tmatsuo commented on May 5, 2020

    @tmatsuo
    Contributor

    I think we haven't seen this failure for a while.
    Maybe we can close this, and see how flaky it is now.

  13. locked as resolved and limited conversation to collaborators on May 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: cloudiotIssues related to the IoT Core API.priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions