Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
S
swiftshader
  • 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
  • swiftshader
  • Repository

Switch branch/tag
  • swiftshader
  • tests
  • regres
  • ci-tests.json
Find file
BlameHistoryPermalink
  • Nicolas Capens's avatar
    Regres: Remove GLES tests from CI test runs · 9677c6d2
    Nicolas Capens authored Feb 06, 2021
    The legacy OpenGL ES implementation is deprecated in favor of SwANGLE,
    and we haven't touched the GLES code in many months. These CI tests
    consume valuable time, and tend to be flaky due to exhausting the
    number of X handles. We still have our 'daily' test runs to provide
    detection of regressions, so they can be safely removed from the CI
    test runs.
    
    Note that this change can also be (temporarily) reverted as part of a
    new change which could use CI testing of dEQP-GLES.
    
    Bug: b/153322216
    Change-Id: I52cd2b89c04c95de486d85118edef6460ba82925
    Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/52532
    Presubmit-Ready: Nicolas Capens <nicolascapens@google.com>
    Tested-by: 's avatarNicolas Capens <nicolascapens@google.com>
    Reviewed-by: 's avatarAntonio Maiorano <amaiorano@google.com>
    9677c6d2
ci-tests.json 1.03 KB
EditWeb IDE
×

Replace ci-tests.json

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.