googleapis
bigtable: TestIntegration_DataMaterializedView failed
Note: #12518 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: b3b8f70a15ae477885f3ecc92e01ae37b7505de3 buildURL: Build Status, Sponge status: failed
![flaky-bot[bot] avatar](https://avatars.githubusercontent.com/in/49504?v=4 "Published by a pub.dev verified publisher"){kind=small}
Test passed for commit 56d1157a9b16d1ec25e8ceedbf0b551610a5ee53 (Build Status, Sponge)! Closing this issue.
Looks like this issue is flaky. :worried:
I'm going to leave this open and stop commenting.
A human should fix and close this.
commit: c9c2abaefd8cc61392aa344ea832851ce2260d8a buildURL: Build Status, Sponge status: failed
Test is no longer flaky
go test -v -timeout 45m -count=10 -run ^TestIntegration_DataMaterializedView$ .
Note: when using prod, you must first create an instance:
cbt createinstance instance01 instance01 instance01-c1 us-central1-b 1 SSD
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (157.27s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (154.08s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (150.35s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (119.27s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (125.17s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (124.81s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (85.73s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (146.64s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (156.21s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (104.44s)
PASS
ok cloud.google.com/go/bigtable 1325.293s
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: 3054593d1f59a65c822a0cf7b8f78440f6234a1d buildURL: Build Status, Sponge status: failed
This seems to be causing continuous to timeout again:
=== RUN TestIntegration_DataMaterializedView
2025/10/08 07:36:26 gRPC metrics failed due permission issue: rpc error: code = PermissionDenied desc = Permission monitoring.timeSeries.create denied (or the resource may not exist).
panic: test timed out after 45m0s
running tests:
TestIntegration_DataMaterializedView (1m36s)
@bhshkh could you take a look
Issue no longer reproducible:
go test -v -count=10 -timeout 45m -run ^TestIntegration_DataMaterializedView$
Note: when using prod, you must first create an instance:
cbt createinstance instance01 instance01 instance01-c1 us-central1-b 1 SSD
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (122.09s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (151.81s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (105.69s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (99.68s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (173.45s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (139.76s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (118.02s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (143.83s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (191.06s)
=== RUN TestIntegration_DataMaterializedView
--- PASS: TestIntegration_DataMaterializedView (155.10s)
PASS
ok cloud.google.com/go/bigtable 1402.106s
Oops! Looks like this issue is still flaky. It failed again. :grimacing:
I reopened the issue, but a human will need to close it again.
commit: 106fc737d0f7f7beb9984cc98b5978d23f9867ca buildURL: Build Status, Sponge status: failed