Kurtiscwright opened a new issue, #18215:
URL: https://github.com/apache/iceberg/issues/18215
### Apache Iceberg version
main (development)
### Query engine
Other
### Please describe the bug 🐞
`RESTCompatibilityKitCatalogTests` and `RESTCompatibilityKitViewCatalogTests`
start their local `RESTCatalogServer` through
`@ExtendWith(RESTServerExtension.class)`,
which uses the fixed default port 8181
(`RESTCatalogServer.REST_PORT_DEFAULT`).
The kafka-connect integration tests publish their REST catalog container on
host port 8181 as well (`kafka-connect-runtime/docker/docker-compose.yml`).
With `org.gradle.parallel=true` (the default in `gradle.properties`) the two
test tasks can overlap on a host that has `docker compose`, and whichever
binds second fails.
Hit while verifying the 1.12.0 RC1 source tarball with `./gradlew build` on
Amazon Linux 2 x86_64, Corretto 17.0.20.1, Docker Compose v2.36.2:
:iceberg-open-api:test
RESTCompatibilityKitCatalogTests > initializationError FAILED
java.io.UncheckedIOException: Failed to start REST server
Caused by: java.net.BindException: Address already in use
Any other process holding 8181, for example a developer running the REST
catalog quickstart locally, produces the same failure.
Expected: `:iceberg-open-api:test` does not depend on port 8181 being free.
The Spark and Flink catalog test bases already avoid this by registering
`RESTServerExtension` with `RESTServerExtension.FREE_PORT`; the RCK tests
should do the same.
Reproduce without docker: hold the port (`python3 -m http.server 8181
--bind 127.0.0.1`) and run `./gradlew :iceberg-open-api:test`.
### Willingness to contribute
- [x] I can contribute a fix for this bug independently
- [ ] I would be willing to contribute a fix for this bug with guidance from
the Iceberg community
- [ ] I cannot contribute a fix for this bug at this time
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
