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_gles3_test_expectations.txt
Find file
BlameHistoryPermalink
  • Kenneth Russell's avatar
    Revert "Supress failures for the 16.12.1 Windows AMD D3D11 driver." · 2a19313f
    Kenneth Russell authored Dec 22, 2016
    This reverts commit e2d0e41f.
    
    Reason for revert: The driver on these machines has been rolled back to the previous version, so these tests are expected to pass again.
    
    Original change's description:
    > Supress failures for the 16.12.1 Windows AMD D3D11 driver.
    > 
    > BUG=676333
    > 
    > Change-Id: I2c29b3dd4ee00bb68575371fe3b1320aad087575
    > Reviewed-on: https://chromium-review.googlesource.com/422479
    > Reviewed-by: Geoff Lang <geofflang@chromium.org>
    > 
    
    TBR=geofflang@chromium.org
    BUG=676333
    NOPRESUBMIT=true
    NOTREECHECKS=true
    NOTRY=true
    
    Change-Id: Ia2952ef55002201dc8c34a4f45c2483bffbf6f43
    Reviewed-on: https://chromium-review.googlesource.com/423126Reviewed-by: 's avatarKenneth Russell <kbr@chromium.org>
    2a19313f
deqp_gles3_test_expectations.txt 29.6 KB
EditWeb IDE
×

Replace deqp_gles3_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.