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.
Running rteval on an 8.1 RT kernel generates a Python backtrace at the end of the run (during report generation I think):
# rteval --duration=2m
got system topology: 2 node system (10 cores per node)
rteval run on 4.18.0-80.11.2.rt9.157.el8_0.x86_64 started at Fri Sep 20 12:36:57 2019
started 2 loads on 20 cores with 2 numa nodes
started measurement threads on 20 cores
Run duration: 120.0 seconds
Exception in thread cyclictest:
Traceback (most recent call last):
File "/usr/lib64/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/usr/lib/python3.6/site-packages/rteval/modules/__init__.py", line 202, in run
self._WorkloadCleanup()
File "/usr/lib/python3.6/site-packages/rteval/modules/measurement/cyclictest.py", line 353, in _WorkloadCleanup
self.__cyclicdata[core].bucket(index, int(vals[i+1]))
IndexError: list index out of range
stopping run at Fri Sep 20 12:39:32 2019
Running rteval on an 8.1 RT kernel generates a Python backtrace at the end of the run (during report generation I think): # rteval --duration=2m got system topology: 2 node system (10 cores per node) rteval run on 4.18.0-80.11.2.rt9.157.el8_0.x86_64 started at Fri Sep 20 12:36:57 2019 started 2 loads on 20 cores with 2 numa nodes started measurement threads on 20 cores Run duration: 120.0 seconds Exception in thread cyclictest: Traceback (most recent call last): File "/usr/lib64/python3.6/threading.py", line 916, in _bootstrap_inner self.run() File "/usr/lib/python3.6/site-packages/rteval/modules/__init__.py", line 202, in run self._WorkloadCleanup() File "/usr/lib/python3.6/site-packages/rteval/modules/measurement/cyclictest.py", line 353, in _WorkloadCleanup self.__cyclicdata[core].bucket(index, int(vals[i+1])) IndexError: list index out of range stopping run at Fri Sep 20 12:39:32 2019