Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
A
angle
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • angle
  • Repository

Switch branch/tag
  • angle
  • src
  • tests
  • deqp_support
  • deqp_gles2_test_expectations.txt
Find file
BlameHistoryPermalink
  • Corentin Wallez's avatar
    Update the dEQP GLES2/3 test expectations · 771f307f
    Corentin Wallez authored May 19, 2016
    Removed the tests that didn't fail in the latest 20 runs on the bots,
    skipping a couple test categories that are known to flake with a very
    low probability. Some flakes might still go through and will have to be
    resuppressed later.
    
    BUG=angleproject:504
    BUG=angleproject:1027
    BUG=angleproject:1032
    BUG=angleproject:1051
    BUG=angleproject:1092
    BUG=angleproject:1093
    BUG=angleproject:1095
    BUG=angleproject:1097
    BUG=angleproject:1101
    BUG=angleproject:1143
    BUG=angleproject:1323
    BUG=angleproject:1324
    
    Change-Id: I5943cd5bc125c64a45ad383c8bf22e48596a4f7e
    Reviewed-on: https://chromium-review.googlesource.com/346050Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
    Commit-Queue: Corentin Wallez <cwallez@chromium.org>
    771f307f
deqp_gles2_test_expectations.txt 16.4 KB
EditWeb IDE
×

Replace deqp_gles2_test_expectations.txt

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.