Bug 47037 - [ILK]Oglc bexact(basic.polyLine) randomly fails
Summary: [ILK]Oglc bexact(basic.polyLine) randomly fails
Status: CLOSED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: All Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-07 00:50 UTC by lu hua
Modified: 2015-06-16 02:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description lu hua 2012-03-07 00:50:38 UTC 
System Environment:
--------------------------
Arch:             i386
Platform:         Ironlake
Libdrm:		 (master)2.4.31-10-gbe30d350b64c1a83473a9ffbedf8e2c680a65fcd
Mesa:		 (master)058fc6521e3bc483bc948cc90dc5ee3b08d6ec64
Libva_intel_driver: (vaapi-ext)304bf4dd752c5d0edd6bcdf87efaaa7db503a1c3
Kernel:	 (drm-intel-next-queued) fa37d39e4c6622d80bd8061d600701bcea1d6870

Bug detailed description:
-----------------------------
The teat result is unstable. I run it 20 times. It fails 9 times, and passes 11 times.
It happens at mesa 8.0 branch and mesa master branch on Ironlake.

Visual used for this test:
ID      |ACCELERA|DB      |REND_T  |SURF_T  |C_BUF_T |BUF_S   |RED_S   |
     105|       1|       0|      gl|  wipbpx|    rgba|      24|       8|

GREEN_S |BLUE_S  |ALPHA_S |DEPTH_S |STENC_S |ACCUM_S |SPL_BUF |SAMPLES |
       8|       8|       0|       0|       0|       0|       0|       0|

SRGB    |TEX_RGB |TEX_RGBA|CAVEAT  |SWAP    |M_PBUF_W|M_PBUF_H|M_PBUF_P
      -1|       0|       0|    none|   undef|       0|       0|       0

Reproduce steps:
----------------------------
1. start X
2. ./oglconform -z -s -suite all -v 2 -test bexact basic.polyLine
Comment 1 Eric Anholt 2012-08-06 19:14:20 UTC 
Doesn't sound like it's a regression, and GL_FRONT_AND_BACK line behavior is quite uninteresting.
Comment 2 Gordon Jin 2015-06-16 02:06:35 UTC 
closing as won't fix.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.