[Failing Test]: JmsIO tests flaky due to port occupied - Githubissues

apache / beam

Apache Beam is a unified programming model for Batch and Streaming data processing.

https://beam.apache.org/

Apache License 2.0

7.76k stars 4.21k forks source link

[Failing Test]: JmsIO tests flaky due to port occupied #26203

Open Abacn opened 1 year ago

Abacn commented 1 year ago

What happened?

These tests use hard coded port 5672 for Jms connection: https://github.com/apache/beam/blob/08f87c6f6a8f06886167bd6bccf325252d3bb8c7/sdks/java/io/jms/src/test/java/org/apache/beam/sdk/io/jms/JmsIOTest.java#L126

If one Jenkins worker happens to run two JmsIO test suite at the same time, the later one will fail, e.g. https://ci-beam.apache.org/job/beam_PreCommit_Java_Jms_IO_Direct_Commit/563/

java.io.IOException: Failed to bind to server socket: amqp://localhost:5672?transport.transformer=jms due to: java.net.BindException: Address already in use (Bind failed)

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
[X] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[X] 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

Abacn commented 1 year ago

Introduced in #25945