From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 107448] [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64,
mesa-18.1.5)
Date: Wed, 01 Aug 2018 18:36:08 +0000
Message-ID:
Bug ID
107448
Summary
[r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-18=
.1.5)
Product
Mesa
Version
unspecified
Hardware
PowerPC
OS
Linux (All)
Status
NEW
Severity
normal
Priority
medium
Component
Drivers/Gallium/r600
Assignee
dri-devel@lists.freedesktop.org
Reporter
erhard_f@mailbox.org
QA Contact
dri-devel@lists.freedesktop.org
Created attachment 140928 [details]=
results from 'pigllit run sanity' (18.1.5)
Machine is a PowerMac G5 11,2 + Radeon HD 6450.
Command
/root/build/piglit/bin/shader_runner
/root/build/piglit/test/spec/arb_tessellation_shader/execution/sanity.shade=
r_test
-auto -fbo
Stdout=20=20
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 25 25 25 25
Test failure on line 57
Stderr=20=20
Mesa: User error: GL_INVALID_ENUM in
lGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)
Command
/root/build/piglit/bin/glsl-1.50-transform-feedback-builtins -auto -fbo
Stdout=20=20
Incorrect data for 'gl_Layer' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_Layer' output 1. Expected 3, got 50331648.
Incorrect data for 'gl_Layer' output 2. Expected 5, got 83886080.
Incorrect data for 'gl_ViewportIndex' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_ViewportIndex' output 1. Expected 2, got 33554432.
Incorrect data for 'gl_ViewportIndex' output 2. Expected 3, got 50331648.<=
/pre>
Created attachment 140929 [deta=
ils]
html-summary from 'pigllit run sanity' (18.1.5)
Observation: bswap32(16777216) =3D=3D 1 bswap32(50331648) =3D=3D 3 bswap32(83886080) =3D=3D 5 For the second test, probably some TF thing that needs to either be configu= red for BE or get byte-swapped somewhere.
Hm, so you think the sanity test itself got broken and not a r= 600g component? I am no expert, sorry.
(In reply to erhard_f from comment #3) > Hm, so you think the sanity test itself got brok= en and not a r600g > component? I am no expert, sorry. No clue. Just an observation for someone who will maybe at one point look i= nto it.
Created attachment 140950 [deta= ils] html-summary from 'pigllit run sanity' (18.0.5) Same test failures with mesa 18.0.5. So I guess it's piglit itself failing,= as at the time I did first piglit tests with 18.0.x on ppc64 (see bug #105463) the sanity tests passed.
| What | Removed | Added |
|---|---|---|
| See Also | https://bugs.freedesktop.org/show_bug.cgi?id=3D107470 |
Meanwhile, on another machine (Talos II + Radeon HD 6450), ano=
ther mesa
(18.2.2) and rebuilt piglit from git-master. But same test-failures here.=
pre>
| What | Removed | Added |
|---|---|---|
| Summary | [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-1= 8.1.5) | [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-1= 8.2.2) |
| What | Removed | Added |
|---|---|---|
| Attachment #140929 is obsolete= td> | 1 | |
| Attachment #140950 is obsolete= td> | 1 |
Created attachment 143610 [deta=
ils]
html-summary from 'pigllit run sanity' (18.3.4)
| What | Removed | Added |
|---|---|---|
| Attachment #140928 is obsolete= td> | 1 |
Created attachment 143611 [details]=
results from 'pigllit run sanity' (18.3.4)
As mesa progresses, piglit sanity tests error count on ppc64 progresses. ;)
Command=20=20=20=20=20=20=20=20=20
/root/build/piglit/bin/shader_runner
/root/build/piglit/tests/spec/arb_tessellation_shader/execution/sanity.shad=
er_test
-auto -fboStderr=20=20=20=20=20=20=20=20
Stderr
Mesa: User error: GL_INVALID_ENUM in
glGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)
Stdout=20=20
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 25 25 25 25
Test failure on line 57
Command=20=20=20=20=20=20=20=20=20
/root/build/piglit/bin/shader_runner
/root/build/piglit/generated_tests/spec/arb_tessellation_shader/execution/b=
uilt-in-functions/tcs-any-bvec4-using-if.shader_test
-auto -fbo
Stderr=20=20
Mesa: User error: GL_INVALID_ENUM in
glGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)
Stdout=20=20
Probe color at (0,0)
Expected: 0 0 255 255
Observed: 0 0 255 0
Test failure on line 92
Probe color at (4,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 93
Probe color at (8,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 94
Probe color at (12,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 95
Probe color at (16,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 96
Probe color at (20,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 97
Probe color at (24,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 98
Probe color at (28,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 99
Probe color at (32,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 100
Probe color at (36,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 101
Probe color at (40,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 102
Probe color at (44,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 103
Probe color at (48,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 104
Probe color at (52,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 105
Probe color at (56,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 106
Probe color at (60,0)
Expected: 1.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 107
Command=20=20=20=20=20=20=20=20=20
/root/build/piglit/bin/shader_runner
/root/build/piglit/tests/spec/arb_tessellation_shader/execution/barrier-pat=
ch.shader_test
-auto -fbo
Stderr=20=20
Mesa: User error: GL_INVALID_ENUM in
glGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)
Stdout=20=20
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 0 0 0 255
Test failure on line 79
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 0 0 0 255
Test failure on line 86
Command=20=20=20=20=20=20=20=20=20
/root/build/piglit/bin/glsl-1.50-transform-feedback-builtins -auto -fbo
Stderr
Stdout=20=20
Incorrect data for 'gl_Layer' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_Layer' output 1. Expected 3, got 50331648.
Incorrect data for 'gl_Layer' output 2. Expected 5, got 83886080.
Incorrect data for 'gl_ViewportIndex' output 0. Expected 1, got 16777216.
Incorrect data for 'gl_ViewportIndex' output 1. Expected 2, got 33554432.
Incorrect data for 'gl_ViewportIndex' output 2. Expected 3, got 50331648.
Command=20=20=20=20=20=20=20=20=20
/root/build/piglit/bin/shader_runner
/root/build/piglit/generated_tests/spec/amd_shader_trinary_minmax/execution=
/built-in-functions/tcs-max3-vec4-vec4-vec4.shader_test
-auto -fbo
Stderr=20=20
Mesa: User error: GL_INVALID_ENUM in
glGetFramebufferAttachmentParameteriv(invalid attachment GL_NONE)Stdout=20=
=20=20=20
Probe color at (0,0)
Expected: 0 255 0 255
Observed: 0 0 255 0
Test failure on line 160
Probe color at (4,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 161
Probe color at (8,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 162
Probe color at (12,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 163
Probe color at (16,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 164
Probe color at (20,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 165
Probe color at (24,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 166
Probe color at (28,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 167
Probe color at (32,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 168
Probe color at (36,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 169
Probe color at (40,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 170
Probe color at (44,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 171
Probe color at (48,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 172
Probe color at (52,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 173
Probe color at (56,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 174
Probe color at (60,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 1.000000 0.000000
Test failure on line 175
| What | Removed | Added |
|---|---|---|
| Summary | [r600g] 2 of 5 piglit sanity tests fail (PCIe, ppc64, mesa-1= 8.2.2) | [r600g] 5 of 30 piglit sanity tests fail (PCIe, ppc64, mesa-= 18.3.4) |
According to on Commen= t 1 on bug #107470 this is most probably = not a piglit bug itself, but a driver bug.
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/642.