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
8237388: serviceability/dcmd/framework/VMVersionTest.java fails with connection refused error. #4235
Conversation
👋 Welcome back amenkov! A progress list of the required criteria for merging this PR into |
@alexmenkov The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
@@ -48,7 +48,7 @@ public static void main(String argv[]) { | |||
log("Waiting for the quit command from the test ..."); | |||
String cmd = pipe.readln(); | |||
int exitCode = PASSED; | |||
if (cmd.equals("quit")) { | |||
if ("quit".equals(cmd)) { |
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 don't see how this is an improvement.
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.
Working on the fix I got null cmd here.
I think "Invalid command received null" failure is clearer than NPE
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
@alexmenkov 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 103 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. ➡️ To integrate this PR with the above commit message to the |
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.
Hi Alex,
This is nice refactoring. It looks good to me.
The fix has a potential to introduce new regressions.
I hope you run all the impacted tests on all platforms.
Thanks,
Serguei
if (listenerThread == null) { | ||
// start listening and accept connection on the current thread | ||
listenerThread = new ListenerThread(); | ||
listenerThread.run(); |
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 is not clear, why listenerThread.run()
is used instead of listenerThread.start()
as at the line 257.
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 part of the workaround for non-updated tests - the tests should work the same way they did.
start() would start new thread, so listening starts a bit later and we have more chances to get "connection refused" error.
} else { | ||
connection.setServerSocket(serverSocket); | ||
// listenerThread == null means the test is not updated yet | ||
// to start IOPipe listening before launching debuggee. |
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 like this workaround for non-updated tests. This spot can be simplified after all tests got updated.
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.
Yes, the plan is to put assert here later.
/integrate |
@alexmenkov Since your change was applied there have been 174 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit b568e87. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
nsk test framework for testing jdi/jdwp assumes that the test launch debuggee first and then creates IOPipe to communicate with debuggee (debugger listens, debugee connects to the IOPipe socket).
This makes possible failure when debuggee tries to connect before debugger starts listening.
The fix changes logic of the tests to start listening on IOPipe socket before launch debuggee.
Other tests which use IOPipe/SocketIOPipe and have the same issue (there are a lot of them) will be fixes as separate issues.
Couple details about the fix:
Testing: all tests which use IOPipe/SocketIOPipe classes:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4235/head:pull/4235
$ git checkout pull/4235
Update a local copy of the PR:
$ git checkout pull/4235
$ git pull https://git.openjdk.java.net/jdk pull/4235/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4235
View PR using the GUI difftool:
$ git pr show -t 4235
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4235.diff