Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This is part one of a fix to prevent tests from failing silently. We would rather have rteval exit with an error, instead of user getting unrealistic test results.
DescriptionGreeshma Gopinath
2016-09-28 18:45:43 UTC
Description of problem:
Automated testing environments need to have consistent tests running every time. Rteval warnings like failure to run hackbench stress due to low memory, might go undetected but they impact the accuracy of the results.There should be an option to trigger a failure in case of warnings.
How reproducible:
Always
Steps to Reproduce:
1.Run rteval when there is less than 1Gb alloted per vcpu
2.Hackbench test does not run because of low memory
3.Other stresses/loads continue to run.
Actual results:
Warning is generated.
Expected results:
The test should have failed because of low memory.
I see that in the particular case of hackbench, if there is an OSError due to not enough memory, hackbench is sleeping and waiting to see if some memory is freed up, which might be okay in a server environment, but not what we want in a low-memory environment. This might be more the source of your problem, so I'm investigating whether there is a solution other than the proposed one.
It appears that this is of no help in a server environment either, so the solution is to remove this code and let rteval fail with an OSError due to not enough memory.
Fixed in 2.14-4 and up
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0969