-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8301306: java/net/httpclient/* fail with -Xcomp #12282
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
Conversation
…ion: HTTP/1.1 header parser received no bytes
👋 Welcome back sunny868! A progress list of the required criteria for merging this PR into |
Webrevs
|
/label core-libs |
@dcubed-ojdk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not the right fix for this kind of problem.
@@ -1437,7 +1437,6 @@ void Arguments::set_mode_flags(Mode mode) { | |||
break; | |||
case _comp: | |||
UseInterpreter = false; | |||
BackgroundCompilation = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disabling BackgroundCompilation
when -Xcomp is specified is not the right
answer here. When -Xcomp
is specified, -Xbatch
needs to be turned off
and I believe that's what old L1440 is doing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dan is right, you can't change the definition of -Xcomp.
But -Xbatch
is -XX:-BackgroundCompilation
. So the second Dan's statement is incorrect.
/label add hotspot-compiler |
@dcubed-ojdk |
There was some discussion about these test failures in the JBS issue and I think @sunny868 has accepted that they need to be investigated to see if they are test reliability issues or something else. As always, running tests with -Xcomp can often challenge timeouts and assumption of progress in tests. |
Yes, -Xcomp can cause long time execution since it we compile all executed methods. But it should not affect execution unless Java code depends on time itself which it should not do. |
/label add net |
@AlanBateman |
@AlanBateman |
@AlanBateman |
@AlanBateman |
@@ -35,7 +35,7 @@ | |||
* @run main/othervm/timeout=600 | |||
* -Dsun.net.httpserver.nodelay=true | |||
* -Dsun.net.client.defaultConnectTimeout=5000 | |||
* -Dsun.net.client.defaultReadTimeout=5000 | |||
* -Dsun.net.client.defaultReadTimeout=50000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this one, it might be simpler to just drop the setting of the defaultReadTimeout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I'll test it on my local machine later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
The following two tests have the same issue, can I submit the fix code to the same patch? |
StructuredTaskScopeTest runs 46 tests, and runs them for both platform and virtual threads. Which test is failing? There is no information in the JBS issue on this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The proposed changes look reasonable to me.
test StructuredTaskScopeTest.testInterruptJoinUntil1(java.lang.ThreadBuilders$PlatformThreadFactory@6e8e0c75): failure |
RFR, thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update and creating JBS issues/PRs for the -Xcomp vs. timeout issues in tests in other areas.
|
@sunny868 This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 101 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@dcubed-ojdk, @dfuch, @AlanBateman) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@AlanBateman Could you please sponsor it for me? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/sponsor |
Going to push as commit 6f9106e.
Your commit was automatically rebased without conflicts. |
@DamonFool @sunny868 Pushed as commit 6f9106e. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
@@ -30,6 +30,7 @@ | |||
* @build jdk.httpclient.test.lib.common.HttpServerAdapters | |||
* jdk.httpclient.test.lib.http2.Http2TestServer | |||
* jdk.test.lib.net.SimpleSSLContext | |||
* @requests (vm.compMode != "Xcomp") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't notice this change while reviewing - it is causing trouble in the CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is PR #12399 related?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it - is that RMI test in #12399 using an HttpServer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that here @requests
should have been @requires
; proposed fix #12409
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WRT #12399: FilterUROTest does NOT use an HttpServer.
It runs as "testng/othervm" so perhaps if jtreg uses an HttpServer there may be a connection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry for my low-level typo ;-(
Hi all,
I think
BackgroundCompilation
should not be set to false when-Xcomp
be used, which causes the java thread to block for longer, then causing the following tests failed frequently on the AArch64 and LoongArch64 architecture.java/net/vthread/HttpALot.java (release -Xcomp)
java/net/httpclient/ByteArrayPublishers.java (fastdebug -Xcomp)
java/net/httpclient/ManyRequestsLegacy.java (fastdebug -Xcomp)
java/net/httpclient/HttpClientLocalAddrTest.java (fastdebug -Xcomp)
java/net/httpclient/SpecialHeadersTest.java (fastdebug -Xcomp)
This PR fix the issue, Please help review it.
Thanks.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/12282/head:pull/12282
$ git checkout pull/12282
Update a local copy of the PR:
$ git checkout pull/12282
$ git pull https://git.openjdk.org/jdk pull/12282/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 12282
View PR using the GUI difftool:
$ git pr show -t 12282
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/12282.diff