Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 611409

Summary: Test Suite should collect the information about the current used video controller
Product: [Retired] Red Hat Hardware Certification Program Reporter: Jianwei Weng <jweng>
Component: Test Suite (harness)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: medium Docs Contact:
Priority: low    
Version: 5.3CC: czhang, gbai, hwcert-reviewers, rlandry, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
An enhancement has been made in v7 1.5 that video test will collect the information about the current in-use video controller by running xvinfo, xdriinfo, and glxinfo.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-05 21:35:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 767775, 773756, 773757    
Attachments:
Description Flags
video test patch adding logging of glxinfo renderer
none
patch to grab output from xvinfo, xdriinfo, and glxinfo, none

Description Jianwei Weng 2010-07-05 07:21:15 UTC
sometimes vendor plug more than 1 video card into the machine,and it's hard for reviewers to determine which one is used for testing.We can check the video card info in the etc/X11/xorg.conf,but it'll be inaccurate if vendor change it mannually.In this case,we want to test suite can provide us the video controller information by the command "glxinfo | grep renderer".

-wjw

Comment 1 Greg Nichols 2010-07-06 16:59:11 UTC
Created attachment 429837 [details]
video test patch adding logging of glxinfo renderer

Comment 2 Rob Landry 2010-07-07 18:41:39 UTC
glxinfo reports on the current 3D render engine not on the current 2D display environment so I don't think it provides what $summary is asking for.

We can add a call to glxinfo on the idea that more information is better however perhaps we should check 1st to verify mesa is even installed (3D testing is not a requirement); also we need to ensure the reviewers properly parse this information as there is no requirement that the 3D hardware be the same device as the 2D hardware.

Comment 6 Rob Landry 2010-07-29 17:56:23 UTC
Moving to v7-1.3 as I think it's more appropriate at this point.

Kevin, we grab the startx logs already, however I don't think we have any automatic parsing in it. One of the things as I recall is that every driver prints out different types and formatted data making that seemingly not so reliable.  We could probably update to grab the associated /var/log file if that would be better.

Comment 10 Rob Landry 2012-03-28 22:05:54 UTC
Created attachment 573482 [details]
patch to grab output from xvinfo, xdriinfo, and glxinfo,

Tested to not crash on this box, but also this is running vesa so these commands don't do much.

Comment 14 Caspar Zhang 2012-06-04 07:02:23 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
An enhancement has been made in v7 1.5 that video test will collect the information about the current in-use video controller by running xvinfo, xdriinfo, and glxinfo.

Comment 16 errata-xmlrpc 2012-06-05 21:35:35 UTC
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.

http://rhn.redhat.com/errata/RHBA-2012-0711.html