Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 3.4k
    • Issues 3.4k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1.1k
    • Merge requests 1.1k
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.

  • MesaMesa
  • mesamesa
  • Issues
  • #1996

[Bisected] WebGL2 failures with Intel Iris driver

There are several failures caught in recent WebGL 2.0 conformance test with Iris driver. They were tested on Coffee Lake (Intel UHD Graphics 630), Ubuntu 19.10 and latest master Mesa (commit: 290b827c1cfe0e99558cf1351bbb8ad2ea678bc0). Steps to repro:

  1. Download nightly Chromium from https://download-chromium.appspot.com/. We couldn't repro this issue with official channel of Chrome (including Dev/Beta/Stable) yet, and I don't know the exact reason. But a big diff is nightly build already switched to use ANGLE while the official build doesn't use ANGLE by default.
  2. Visit Khronos WebGL 2.0 website: https://www.khronos.org/registry/webgl/sdk/tests/webgl-conformance-tests.html?version=2.0.1.
  3. Run one of below cases: conformance/rendering/out-of-bounds-array-buffers.html (flaky) conformance2/rendering/element-index-uint.html (flaky) conformance2/rendering/out-of-bounds-index-buffers-after-copying.html (flaky) conformance2/rendering/blitframebuffer-filter-outofbounds.html (always failed)

flaky means we need to run the case more than once before hitting a failure. However, for these flaky cases, it's still easy to repro within 10 runs.

  1. You may see some failures now while these cases all passed on i965 driver steadily.
Edited Oct 28, 2019 by Paul Che
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking