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
  • perf_tests
  • TracePerfTest.cpp
Find file
BlameHistoryPermalink
  • Jamie Madill's avatar
    Trace Tests: Screenshot within the render loop. · ae5a2047
    Jamie Madill authored Nov 20, 2020
    Previously we were using a separate mechanism to capture screen
    shots. This would cause very long traces to replay the entire
    trace before normal execution. The Maps trace used hundreds of
    frames and this was timing out the test step.
    
    Instead we can capture a screenshot after the first time we run
    a trace. This will normally not interfere with performance work
    because we don't usually capture screenshots and do performance
    work at the same time.
    
    Bug: b/172977194
    Change-Id: I12cfe2d051d41f1e000a98ac8aef16eb153879c0
    Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2552925Reviewed-by: 's avatarCody Northrop <cnorthrop@google.com>
    Commit-Queue: Jamie Madill <jmadill@chromium.org>
    ae5a2047
TracePerfTest.cpp 28.8 KB
EditWeb IDE
×

Replace TracePerfTest.cpp

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.