-
Notifications
You must be signed in to change notification settings - Fork 155
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
8253435: Cgroup: 'stomping of _mount_path' crash if manually mounted cpusets exist #158
Conversation
👋 Welcome back jdowland! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
This one will need changes. Build fails with:
|
hotspot/test/runtime/containers/cgroup/CgroupSubsystemFactory.java
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.
There seems to be a problem with this PR. It shows commits not part of this PR, but others (e.g. #135). The bot is also not happy about it. Before this can get properly reviewed, this would need some fixup.
@@ -256,5 +256,8 @@ public int getOffsetForName(String name) throws Exception { | |||
// Container testing | |||
public native boolean isContainerized(); | |||
public native void printOsInfo(); | |||
public native int validateCgroup(String procCgroups, |
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 doesn't look right. It's part of #135. See: https://github.com/openjdk/jdk8u-dev/pull/135/files#diff-840578f66556c33204f36e83d8c5a6b6b91c0280ffdbbea6121847a5b6b1afe7R259
Sorry about that. I think the merge hasn't worked. (I can't confirm that at the time I did it because we have to wait for the bot to update the pr/ branch in the main repository for the web view to show the proper comparison). I'll do a rebase and see what it looks like. |
936609c
to
793364d
Compare
I've rebased but PR 135's commits are still missing in the chain for this one so further work is required to find out where things have gone out of sync. |
9b22583
to
95e430e
Compare
@jmtd Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
95e430e
to
00dc64a
Compare
793364d
to
34b0259
Compare
@jmtd Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
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 looks good now. Thanks!
@jmtd This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
Keep open please. |
00dc64a
to
4ea4662
Compare
34b0259
to
564b1a0
Compare
@jmtd Please do not rebase or force-push to an active PR as it invalidates existing review comments. All changes will be squashed into a single commit automatically when integrating. See OpenJDK Developers’ Guide for more information. |
564b1a0
to
c849e96
Compare
…cpusets exist Backport-of: 0054c15f60cce6470be05d29bfacbdb74cfb7bc9
4ea4662
to
5943791
Compare
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout 8253435-jdk8u-dev
git fetch https://git.openjdk.org/jdk8u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
@jmtd Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
@jmtd This change now passes all automated pre-integration checks. 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 no new commits pushed to the ➡️ 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.
OK. Feel free to integrate and then rebase #159. Thank you!
/integrate |
Going to push as commit 2bee645. |
This is a backport of 8253435 to jdk8u-dev for cgroups v2 support.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/158/head:pull/158
$ git checkout pull/158
Update a local copy of the PR:
$ git checkout pull/158
$ git pull https://git.openjdk.org/jdk8u-dev pull/158/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 158
View PR using the GUI difftool:
$ git pr show -t 158
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/158.diff