Abacn opened a new issue, #26673:
URL: https://github.com/apache/beam/issues/26673
### What happened?
Permared since May 10.
Error message:
```
apache_beam/io/gcp/bigtableio_test.py:84:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
apache_beam/io/gcp/bigtableio_test.py:138: in verify_write_call_metric
self.assertTrue(
E AssertionError: False is not true : Did not find write call metric with
status: already_exists
```
No code change involved. Also, checkout a snapshot prior to May 10 and run
this test locally:
```
pytest -v
apache_beam/io/gcp/bigtableio_test.py::TestWriteBigTable::test_write_metric
```
it fails for the same reason.
Likely due to Bigtable service change
### Issue Failure
Failure: Test is flaky
### Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
