-
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
8272146: Disable Fibonacci test on memory constrained systems #5051
Conversation
👋 Welcome back cgo! A progress list of the required criteria for merging this PR into |
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.
Seems a reasonable constraint.
Thanks,
David
@mychris 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 30 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, @mseledts, @shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Thanks for the reviews. |
/sponsor |
Going to push as commit adba09b.
Your commit was automatically rebased without conflicts. |
Hi,
please review this small change to the Fibonacci test case. I added an additional memory requirement for Linux, as I am seeing the test fail on some embedded and emulated devices which do not have enough memory to execute the test case.
The test succeeds on a device with 512MB of physical memory, so I guess this upper bound should be fine. The problem seems to be the kernel memory, as the devices have enough swap space to handle the other test cases.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5051/head:pull/5051
$ git checkout pull/5051
Update a local copy of the PR:
$ git checkout pull/5051
$ git pull https://git.openjdk.java.net/jdk pull/5051/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5051
View PR using the GUI difftool:
$ git pr show -t 5051
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5051.diff