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]: Firestore integration tests failing affecting GCPIO_PreCommit, DataflowPostCommit V1 and V2 #25851

Closed
2 of 15 tasks
Abacn opened this issue Mar 15, 2023 · 2 comments · Fixed by #27743
Closed
2 of 15 tasks

Comments

@Abacn
Copy link
Contributor

Abacn commented Mar 15, 2023

What happened?

Test Link: https://ci-beam.apache.org/view/PostCommit/job/beam_PostCommit_Java_DataflowV2/lastCompletedBuild/testReport/
More Info:

Many FirestoreIO integration test in the Apache Beam Java PostCommit failing starting March 14 without code change.

Error Message
java.util.concurrent.ExecutionException: com.google.api.gax.rpc.InvalidArgumentException: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Invalid request routing header database=projects/apache-beam-testing/databases/firestoredb. Please fill in the request header with format x-goog-request-params:project_id=apache-beam-testing&database_id=firestoredb

Firestore recently enforced the routing header for named databases. Integration tests need to pass the correct routing header.

Issue Failure

Failure: Test is continually failing

Issue Priority

Priority: 1 (unhealthy code / failing or flaky postcommit so we cannot be sure 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
@kennknowles
Copy link
Member

We need to schedule the work to make tests that work. I am unclear whether we need this at P1. I guess we lost a lot of coverage...

@Abacn
Copy link
Contributor Author

Abacn commented May 17, 2023

Most test are back green and executing again in #26738, except one still failing, waiting for another firestore release.

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