Bug 107742 - [BYT] intermittent failures for piglit.spec.arb_shader_image_load_store.invalid
Summary: [BYT] intermittent failures for piglit.spec.arb_shader_image_load_store.invalid
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: lowest trivial
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-29 20:35 UTC by Mark Janes
Modified: 2019-09-25 19:13 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Janes 2018-08-29 20:35:04 UTC
On BayTrail, this test fails occasionally (~1%) with:

/tmp/build_root/m32/lib/piglit/bin/arb_shader_image_load_store-invalid -auto -fbo
piglit: debug: Requested an OpenGL 3.2 Core Context, and received a matching 4.2 context

Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 0.000000
  Observed: 1.000000 1.000000 1.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 0.000000
  Observed: 1.000000 1.000000 1.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 0.000000 0.000000 0.000000 0.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 1.000000 1.000000 1.000000 1.000000
  Observed: 33.000000 33.000000 33.000000 33.000000
  Source: image
Probe value at (0, 0, 0, 0)
  Expected: 1.000000 1.000000 1.000000 1.000000
  Observed: 33.000000 33.000000 33.000000 33.000000
  Source: image
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 0.000000 0.000000 0.000000 0.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 1.000000
  Observed: 1056980799.000000
  Source: image
Probe value at (0, 0, 0, 0)
  Expected: 1.000000
  Observed: 1056980799.000000
  Source: image
Probe value at (0, 0, 0, 0)
  Expected: 1.000000
  Observed: 1056980799.000000
  Source: image
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 1.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Probe value at (0, 0, 0, 0)
  Expected: 0.000000 0.000000 0.000000 1.000000
  Observed: 2015233024.000000 0.000000 0.000000 1.000000
  Source: framebuffer
Comment 1 GitLab Migration User 2019-09-25 19:13:23 UTC
-- 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/1751.


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.