| commit | 59b6ba9bb2b8a280a30e931fb9b69f492650d14d | [log] [tgz] |
|---|---|---|
| author | Jiayuan Ren <jiayuanr@nvidia.com> | Tue Aug 14 19:09:01 2018 |
| committer | Chris Forbes <chrisforbes@google.com> | Fri Aug 17 23:48:33 2018 |
| tree | dd54a1a910ad159c0f417042fc0db5ec6a8809a8 | |
| parent | 38611cff1bef4332dc1106706c6bd9ced62cff53 [diff] |
Fix: rendering complete times not monotonic We run into an intermittent issue that two neighboring frames have the same rendering complete timestamp. The timers will always have finite granularity. The timestamp is in nanosecond but the timer producing these timestamps might not actually be able to produce timestamps at 1ns resolution. When the timer used for these events has not enough granularity, events that happen very quickly right after one another will appear as if they appear at the same point in time. Two neighboring frames have the same timestamp is allowed. Components: AOSP VK-GL-CTS issue: 1311 Bug: b/112778381 Affects: dEQP-EGL.functional.get_frame_timestamps.*
This repository contains a GPU testing suite called dEQP (drawElements Quality Program). dEQP contains tests for several graphics APIs, including OpenGL ES, EGL, and Vulkan.
Up-to-date documentation for the dEQP is available at Android Open Source Project site.
This repository includes Khronos Vulkan CTS under external/vulkancts directory. For more information see Vulkan CTS README.