Skip to content

[Bug]: Flaky Prism Runner unit tests in Java PreCommit #35233

@Abacn

Description

@Abacn

What happened?

Flaky Prism Runner unit tests in Java PreCommit

Some recent added tests are flaky:

prismReportsPAssertFailure (org.apache.beam.runners.prism.PrismRunnerTest) failed

java.lang.AssertionError: unexpected exception type thrown; expected:<java.lang.AssertionError> but was:<org.apache.beam.vendor.grpc.v1p69p0.io.grpc.StatusRuntimeException>
	at org.junit.Assert.assertThrows(Assert.java:1020)
	at org.junit.Assert.assertThrows(Assert.java:981)
	at org.apache.beam.runners.prism.PrismRunnerTest.prismReportsPAssertFailure(PrismRunnerTest.java:105)
Caused by: org.apache.beam.vendor.grpc.v1p69p0.io.grpc.StatusRuntimeException: UNAVAILABLE: Network closed for unknown reason
	at app//org.apache.beam.vendor.grpc.v1p69p0.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:268)
	at app//org.apache.beam.vendor.grpc.v1p69p0.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:249)

windowing (org.apache.beam.runners.prism.PrismRunnerTest) failed

(same stack trace)

likely due to grpc channel not closed gracefully

e.g. https://github.com/apache/beam/runs/43846630757

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

  • Component: Python SDK
  • Component: Java SDK
  • Component: Go SDK
  • Component: Typescript SDK
  • Component: IO connector
  • Component: Beam YAML
  • Component: Beam examples
  • Component: Beam playground
  • Component: Beam katas
  • Component: Website
  • Component: Infrastructure
  • Component: Spark Runner
  • Component: Flink Runner
  • Component: Samza Runner
  • Component: Twister2 Runner
  • Component: Hazelcast Jet Runner
  • Component: Google Cloud Dataflow Runner

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions