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]: org.apache.beam.sdk.io.gcp.pubsub.PubsubSchemaIT.classMethod in beam_PostCommit_Java_DataflowV1 and V2 #24802

Closed
2 of 15 tasks
Abacn opened this issue Dec 28, 2022 · 2 comments · Fixed by #24803

Comments

@Abacn
Copy link
Contributor

Abacn commented Dec 28, 2022

What happened?

error message:

org.apache.beam.sdk.io.gcp.pubsub.PubsubSchemaIT.classMethod

Error Message
java.nio.file.NoSuchFileException: file:/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Java_DataflowV2/src/sdks/java/io/google-cloud-platform/build/libs/beam-sdks-java-io-google-cloud-platform-2.45.0-SNAPSHOT-tests.jar!/org/apache/beam/sdk/io/gcp/pubsub/avro_all_data_types_flat_schema.json

caused by #24443

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
@damondouglas
Copy link
Contributor

.take-issue

@lukecwik
Copy link
Member

Can we disable the test if the fix is not obvious?

@github-actions github-actions bot added this to the 2.45.0 Release milestone Dec 29, 2022
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