tree 43685410548a8755de91ad7f095a7fb1cd7c2a3d
parent 0db803bc3c95dd824a88064b6a7fbfac86ff471c
author Bill Hollings <bill.hollings@brenwill.com> 1618266016 -0400
committer Bill Hollings <bill.hollings@brenwill.com> 1618266016 -0400

Add MVKConfiguration::resumeLostDevice and MVK_CONFIG_RESUME_LOST_DEVICE env var,
to allow VkDevice to resume after non-fatal VK_ERROR_DEVICE_LOST error.

When running CTS, when one test triggers a VK_ERROR_DEVICE_LOST error condition,
CTS does not create a new VkDevice for subsequent tests, which causes all subsequent
tests to fail. This creates an incredible amount of results noise, and makes it
difficult to determine accurate test failure numbers. This is particularly problematic
because VK_ERROR_DEVICE_LOST may be triggered sporadically by internal Metal issues,
often making it not traceable to a consistent failure of a particular CTS test.