Skip to content
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

Failing test(s): TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval #21167

Open
shuyama1 opened this issue Jan 31, 2025 · 2 comments

Comments

@shuyama1
Copy link
Collaborator

shuyama1 commented Jan 31, 2025

Impacted tests

TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval

Affected Resource(s)

google_bigquery_table

Failure rates

  • GA: 100%
  • Beta: 100%

Message(s)

=== RUN   TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval
=== PAUSE TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval
=== CONT  TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval
    resource_bigquery_table_test.go:1748: Step 1/2 error: After applying this test step and performing a `terraform refresh`, the plan was not empty.
        stdout
        
        
        Terraform used the selected providers to generate the following execution
        plan. Resource actions are indicated with the following symbols:
          ~ update in-place
        
        Terraform will perform the following actions:
        
          # google_bigquery_table.replica_mv will be updated in-place
          ~ resource "google_bigquery_table" "replica_mv" {
                id                       = "projects/ci-test-project-nightly-ga/datasets/tf_test_replica_dataset_fnt63w793m/tables/tf_test_replica_mv_ks6pf3d2rd"
              - max_staleness            = "0-0 0 10:0:0" -> null
                # (22 unchanged attributes hidden)
        
                # (1 unchanged block hidden)
            }
        
        Plan: 0 to add, 1 to change, 0 to destroy.
--- FAIL: TestAccBigQueryTable_TableReplicationInfo_WithReplicationInterval (43.81s)
FAIL

Test Debug Log

b/394096764

@wj-chen
Copy link

wj-chen commented Feb 3, 2025

Looks like the API behavior changed to now return a default max_staleness in the response. I will check with the backend team.

@melinath
Copy link
Collaborator

melinath commented Feb 3, 2025

#21136 is failing for the same reason

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

No branches or pull requests

5 participants