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.

Sign up for GitHub

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

Jump to bottom

[Bug report] JettyTest port flaky conflict issue #392

Closed
xunliu opened this issue Sep 13, 2023 · 0 comments · Fixed by #393
Closed

[Bug report] JettyTest port flaky conflict issue #392

xunliu opened this issue Sep 13, 2023 · 0 comments · Fixed by #393

Comments

@xunliu
Copy link
Member

xunliu commented Sep 13, 2023

Describe what's wrong

Graviton JettyTest uses an automatic allocation Port, if exception test cases are in parallel, it will target the JettyTest port flaky conflict issue.

Error message and/or stacktrace

TestIcebergTableOperations > testCreateTable() FAILED
    org.glassfish.jersey.test.spi.TestContainerException at JettyTestContainerFactory.java:104
        Caused by: java.io.IOException at ServerConnector.java:349
            Caused by: java.net.BindException at Net.java:-2

20 tests completed, 10 failed
> Task :catalog-lakehouse:test FAILED

> Task :server:test
TestCatalogOperations > testLoadCatalog() FAILED
    org.glassfish.jersey.test.spi.TestContainerException at JettyTestContainerFactory.java:104
        Caused by: java.io.IOException at ServerConnector.java:349
            Caused by: java.net.BindException at Net.java:-2

How to reproduce

execution ./gradlew build

Additional context

No response
@xunliu xunliu mentioned this issue Sep 13, 2023
Merged
jerryshao pushed a commit that referenced this issue Sep 14, 2023
@xunliu
[#392] fix(server, catalog-lakehouse): Fix JettyTest port flaky confl…
75448c9 
…ict issue (#393)

### What changes were proposed in this pull request?

+ Find an available port from a port range
+ Randomizing ports from a range of ports to resolve conflicts during
concurrent calls

### Why are the changes needed?

Graviton JettyTest uses an automatic allocation Port, if exception test
cases are in parallel, it will target the JettyTest port flaky conflict
issue.

Fix: #392 

### Does this PR introduce _any_ user-facing change?

N/A

### How was this patch tested?

Added `testFindAvailablePort()` in the `TestRESTUtil.java`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#392] fix(server, catalog-lakehouse): Fix JettyTest port flaky conflict issue
1 participant
@xunliu