Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mesa
mesa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,326
    • Issues 2,326
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 646
    • Merge Requests 646
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Mesa
  • mesamesa
  • Issues
  • #1767

Closed
Open
Opened Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration

flaky results from glescts geometry_shader.layered_rendering_boundary_condition.layered_rendering_boundary_condition_no_default_layer

Submitted by Mark Janes @majanes

Assigned to Jason Ekstrand @jekstrand

Link to original bug (#108571)

Description

On a very intermittent basis, this test (in GLESEXT and GLES32 conformance tests) fails on skl, kbl, and cfl with:

Rendered data for [x=3 y=0 attachment=0 layer=0] [0, 0, 0, 0] are different from reference data [255, 255, 255, 255] !

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mesa/mesa#1767