-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8313770: jdk/internal/platform/docker/TestSystemMetrics.java fails on Ubuntu #27934
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
8313770: jdk/internal/platform/docker/TestSystemMetrics.java fails on Ubuntu #27934
Conversation
|
👋 Welcome back cnorrbin! A progress list of the required criteria for merging this PR into |
|
@caspernorrbin 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 16 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 |
|
@caspernorrbin 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. |
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.
|
Thank you all for the reviews! /integrate |
|
Going to push as commit aec1388.
Your commit was automatically rebased without conflicts. |
|
@caspernorrbin Pushed as commit aec1388. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi everyone,
The test
TestSystemMetrics.javasometimes fails on cgroupv2 when comparing read/write I/O metrics (rios/wios) because the expected value doesn't match the one read from theio.statfile. The current approach in this test is somewhat flawed, it reads from the sameio.statfile cgroup file twice, once directly and once throughjdk.internal.platform.Metrics, and assumes the values should be identical. In practice, this assumption does not hold. Unrelated I/O running in the same cgroup may increment the counter between reads, leading to discrepancies.The current comparisons have a 25% margin from the original value to account for incidental noise, but this doesn't work well on the I/O operation counters, which can have very small values (sometimes as low as 0), which makes the percentage-based margin useless. As a result, this test is at risk of failing whenever activity happens between the 2 file readings.
For greater reliability, I suggest we should instead check that the value is increasing rather than expecting equality. This is already done for other metrics, such as CPU and memory usage, and more accurately reflects the expected behaviour of the counters. Switching to this check removes the reliance on error margins and results in a more stable and meaningful test.
Testing:
TestSystemMetrics.javawithout any observed failures.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27934/head:pull/27934$ git checkout pull/27934Update a local copy of the PR:
$ git checkout pull/27934$ git pull https://git.openjdk.org/jdk.git pull/27934/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27934View PR using the GUI difftool:
$ git pr show -t 27934Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27934.diff
Using Webrev
Link to Webrev Comment