Skip to content

Failing test(s): TestAccBigQueryExternalDataTable_deltaLake #21764

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

Open
modular-magician opened this issue Mar 8, 2025 · 2 comments · May be fixed by GoogleCloudPlatform/magic-modules#13683

Comments

@modular-magician
Copy link
Collaborator

modular-magician commented Mar 8, 2025

Impacted tests

TestAccBigQueryExternalDataTable_deltaLake

Affected Resource(s)

google_bigquery_table

Failure rates

  • GA: 0%
  • Beta: 100%

Message(s)

=== RUN   TestAccBigQueryExternalDataTable_deltaLake
=== PAUSE TestAccBigQueryExternalDataTable_deltaLake
=== CONT  TestAccBigQueryExternalDataTable_deltaLake
    resource_bigquery_table_test.go:797: Step 1/1 error: Error running apply: exit status 1
        
        Error: googleapi: Error 400: The parent directory gs://tf-test-bucket-8075925552690543463/* is not a valid path for a Delta Lake table. Delta log files could not be found in the subdirectory _delta_log and a checkpoint could not be determined., invalidQuery
        
          with google_bigquery_table.test,
          on terraform_plugin_test.tf line 21, in resource "google_bigquery_table" "test":
          21: resource "google_bigquery_table" "test" {
        
--- FAIL: TestAccBigQueryExternalDataTable_deltaLake (9.36s)
FAIL

Test Debug Log

b/409408059

@wj-chen
Copy link

wj-chen commented Apr 10, 2025

Looking into it. There is no change to the test or related provider logic in recent past, so most likely a regression in some dependency. I don't have visibility into the test history - is it still 100% failing in Beta but not GA?

@wj-chen
Copy link

wj-chen commented Apr 10, 2025

Hi @DrFaust92 , we are currently seeing this test failure for BigQuery delta lake tables. I saw that when you added this feature in GoogleCloudPlatform/magic-modules#11215, you saw the same error message and fixed the test in the end. Do you happen to recall anything specific you did or anything in general to share? Thank you.

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

Successfully merging a pull request may close this issue.

3 participants