Skip to content
This repository was archived by the owner on Feb 13, 2026. It is now read-only.
This repository was archived by the owner on Feb 13, 2026. It is now read-only.

tests.unit.test_zone.TestManagedZone: many tests failed #370

Description

@flaky-bot

Many tests failed at the same time in this package.

  • I will close this issue when there are no more failures in this package and
    there is at least one pass.
  • No new issues will be filed for this package until this issue is closed.
  • If there are already issues for individual test cases, I will close them when
    the corresponding test passes. You can close them earlier, if you prefer, and
    I won't reopen them while this issue is still open.

Here are the tests that failed:

  • test_changes
  • test_create_w_alternate_client
  • test_create_w_bound_client
  • test_create_w_missing_output_properties
  • test_create_wo_dns_name_or_description
  • test_ctor_defaults
  • test_ctor_explicit
  • test_ctor_wo_description
  • test_delete_w_alternate_client
  • test_delete_w_bound_client
  • test_description_setter
  • test_description_setter_bad_value
  • test_exists_hit_w_alternate_client
  • test_exists_miss_w_bound_client
  • test_from_api_repr_bare
  • test_from_api_repr_missing_identity
  • test_from_api_repr_w_properties
  • test_list_changes_defaults
  • test_list_changes_explicit
  • test_list_resource_record_sets_defaults
  • test_list_resource_record_sets_explicit
  • test_name_server_set_setter
  • test_name_server_set_setter_bad_value
  • test_reload_w_alternate_client
  • test_reload_w_bound_client
  • test_resource_record_set

commit: 3c02f8e
buildURL: Build Status, Sponge
status: failed

Activity

  1. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.
    on Jan 4, 2026
  2. flaky-bot commented on Jan 5, 2026

    @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.


    When run at the same commit (3c02f8e), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

  3. added
    flakybot: flakyTells the Flaky Bot not to close or comment on this issue.
    on Jan 5, 2026
  4. chalmerlowe commented on Jan 5, 2026

    @chalmerlowe
    Contributor

    Should be fixed by #371

    Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: dnsIssues related to the googleapis/python-dns API.flakybot: flakyTells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.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.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions