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

fix(jetty-client:12.0.0.beta0): resolve test failures #601

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

erguiti-imane
Copy link
Member

What does this PR do?

  • Updated the version of 'org.eclipse.jetty:jetty-client' to 11.0.12 in the testImplementation scope and regenerated metadata.

Checklist before merging

- Updated the version of 'org.eclipse.jetty:jetty-client' to 11.0.12 in the testImplementation scope and regenerated metadata.
@erguiti-imane erguiti-imane requested a review from a team as a code owner February 19, 2025 17:36
@dnestoro
Copy link
Member

dnestoro commented Mar 3, 2025

@fniephaus please review this pull request when possible as we are planning to have a new release of reachability metadata (+Native Build Tools) soon.

@fniephaus fniephaus requested review from mhalbritter and dnestoro and removed request for fniephaus March 3, 2025 15:51
Copy link
Member

@dnestoro dnestoro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks okay. Thanks for your contribution! I just added few minor comments. Please address them and resolve current merge conflicts.

@mhalbritter please review this PR since you added initial metadata and tests for jetty-client

graalvmNative {
binaries {
test {
buildArgs.add('--enable-preview')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you use this build arg?


class JettyClientTest {

private static final String DOCKER_HOST = "127.0.0.1";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use localhost string instead of 127.0.0.1. They represent the same thing, but I see that we usually use "localhost":

"resources":{
"includes":[{
"condition":{"typeReachable":"org.eclipse.jetty.client.http.HttpReceiverOverHTTP"},
"pattern":"\\QMETA-INF/services/org.eclipse.jetty.http.HttpFieldPreEncoder\\E"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be covered by the ServiceLoader integration GraalVM has. Can be removed.

"pattern":"\\Qorg/eclipse/jetty/version/build.properties\\E"
}, {
"condition":{"typeReachable":"org.eclipse.jetty.client.AbstractConnectorHttpClientTransport"},
"pattern":"java.base:\\Qjdk/internal/icu/impl/data/icudt67b/nfc.nrm\\E"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks suspicious. Try to remove it and see if tests still pass.

String libraryVersion = tck.testedLibraryVersion.get()

dependencies {
testImplementation "org.eclipse.jetty:jetty-client:11.0.12"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be $libraryVersion? Right now, the metadata should be for 12.0.0-beta0 but has been tested against 11.0.12?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And I guess even the agent collected it from 11.0.12?

@mhalbritter
Copy link
Collaborator

Hello, i've left some remarks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants