Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1360853

Summary: new failures in piglit test suite for VMWare 11
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Hudziec <thudziec>
Component: mesaAssignee: Dave Airlie <airlied>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.3CC: tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-22 03:19:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tomas Hudziec 2016-07-27 16:05:01 UTC
Filed from caserun https://tcms.engineering.redhat.com/run/288273/#caserun_13120333

Version-Release number of selected component (if applicable):
----------

Steps to Reproduce: 
 1. Do a fresh boot up
 2. Install ResultsDB client:
    # wget -O /etc/yum.repos.d/resultsdb-client.repo http://
    download.eng.brq.redhat.com/scratch/mdomonko/resultsdb/
    resultsdb-client.repo
    # yum install resultsdb-wrappers

 1. Run as a regular user:
    $ piglit-run_and_report


Actual results: 
Regressions found!
Fixed:     76 tests
Regressed: 29 tests
Outcome:   REGRESS
Diff URL:  https://tools.dqe.lab.eng.bos.redhat.com:5000/diff/2040:2343


Expected results:
After the test completes, the script should ask you a couple of questions and
then report your results to ResultsDB for analysis and archiving.

Note: If the script terminates without asking any questions or Xorg crashes/
freezes during the test, this test case FAILED.

After the script finishes, the result of the analysis is printed to the
terminal. If the outcome is

  * GOOD or WARN, set this test case to PASSED and you're done
  * REGRESS, set this test case to FAILED and file a bug report against the
    mesa component (include the provided Diff URL, if any)

Note from David Airlie: Its unlikely we'll ever see a perfect piglit run on any
GL hardware, its probably more of a regression suite, so if a test passes in
RHEL6.1 it should continue to pass in RHEL6.2

Comment 3 Dave Airlie 2018-02-22 03:19:08 UTC
The diffs expired, and we've rebased mesa a couple of times.