Make sure graphics_Drm runs vk_glow |
||
Issue descriptionProbably needs a new control file. See also https://chromium-review.googlesource.com/#/c/387199/
,
May 4 2017
On Snappy test runs for real https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=475989790 05/04 03:45:08.789 DEBUG| utils:0202| Running 'vk_glow' 05/04 03:45:09.182 DEBUG| utils:0297| [stdout] Available VkPhysicalDevices: 05/04 03:45:09.184 DEBUG| utils:0297| [stdout] VkPhysicalDevice 0: 05/04 03:45:09.185 DEBUG| utils:0297| [stdout] apiVersion: 1.0.5 05/04 03:45:09.186 DEBUG| utils:0297| [stdout] driverVersion: 1 05/04 03:45:09.187 DEBUG| utils:0297| [stdout] vendorID: 0x8086 05/04 03:45:09.188 DEBUG| utils:0297| [stdout] deviceID: 0x5a85 05/04 03:45:09.189 DEBUG| utils:0297| [stdout] deviceName: Intel(R) HD Graphics 500 (Broxton 2x6) 05/04 03:45:09.190 DEBUG| utils:0297| [stdout] pipelineCacheUUID: 616e762d-3134-3933-3830-3733393300 05/04 03:45:09.191 DEBUG| utils:0297| [stdout] Chose VkPhysicalDevice 0 05/04 03:45:18.199 DEBUG| test:0381| The test has completed successfully 05/04 03:45:18.201 DEBUG| test:0392| starting after_iteration_hooks Other boards correctly skip https://wmatrix.googleplex.com/unfiltered?hide_missing=True&releases=tot&tests=graphics_Drm.vk_glow |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, May 2 2017