-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
JDK-8219652: [aix] Tests failing with JNI attach problems. #15924
Conversation
👋 Welcome back varada1110! A progress list of the required criteria for merging this PR into |
@varada1110 The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
test/hotspot/jtreg/vmTestbase/nsk/jvmti/scenarios/jni_interception/JI06/ji06t001/ji06t001.cpp
Outdated
Show resolved
Hide resolved
It seems for some of the fixes instead of making sure the current thread has sufficient stack space , you instead create a new thread with sufficient stack space to attach to. Is there a reason the original thread could not have been created with enough stack space? |
test/hotspot/jtreg/vmTestbase/nsk/jvmti/SetJNIFunctionTable/setjniftab001/setjniftab001.cpp
Outdated
Show resolved
Hide resolved
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.
You should be changing the thread creation logic in ./nsk/share/native/native_thread.cpp for the nsk test changes.
Thanks
Thank you @dholmes-ora .I have applied changes there. Please review the code change |
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.
That is much cleaner and simpler - thanks.
A couple of minor nits, plus the ProblemList fixing that Chris mentioned.
test/hotspot/jtreg/vmTestbase/nsk/share/native/native_thread.cpp
Outdated
Show resolved
Hide resolved
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.
That all looks fine to me.
Thanks.
|
@varada1110 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 285 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 (@dholmes-ora, @plummercj, @sspitsyn) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Copyrights need updating. Can you tell me what testing you've done? |
I have performed jtreg testing |
Yes, but what testing and on which platforms? |
I just ran the changes through our tier1 CI and also ran all the nsk/jvmti tests on all supported platforms and everything passed, so I think the changes are good. |
I performed tests on AIX 7.2. Thank you @plummercj for checking on all platforms |
/integrate |
@varada1110 |
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 good.
Thanks,
Serguei
/sponsor |
Going to push as commit 0b0f8b5.
Your commit was automatically rebased without conflicts. |
@offamitkumar @varada1110 Pushed as commit 0b0f8b5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Similar issue JDK-8303549 where AttachCurrentThread is failing on AIX due to stack size issue.
Test cases:
runtime/jni/terminatedThread/TestTerminatedThread.java
vmTestbase/nsk/jvmti/scenarios/jni_interception/JI05/ji05t001/TestDescription.java
vmTestbase/nsk/jvmti/scenarios/jni_interception/JI06/ji06t001/TestDescription.java
vmTestbase/nsk/jvmti/SetJNIFunctionTable/setjniftab001/TestDescription.java
Reported Issue : JDK-8219652
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15924/head:pull/15924
$ git checkout pull/15924
Update a local copy of the PR:
$ git checkout pull/15924
$ git pull https://git.openjdk.org/jdk.git pull/15924/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15924
View PR using the GUI difftool:
$ git pr show -t 15924
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15924.diff
Webrev
Link to Webrev Comment