baldurk ccd5ba218e Explicitly shutdown only the running test, instead of using destructors ...

* The tests are global objects so there's a potential ordering issue of
  destroying these tests after RenderDoc's global destructors have run.

2019-04-04 15:50:34 +01:00

..

gl_buffer_updates.cpp

…

gl_cbuffer_zoo.cpp

…

gl_depthstencil_fbo.cpp

…

gl_dx_interop.cpp

…

gl_large_bcn_arrays.cpp

…

gl_map_overrun.cpp

…

gl_midframe_context_create.cpp

…

gl_mip_gen_rt.cpp

…

gl_multi_window.cpp

…

gl_overlay_test.cpp

…

gl_runtime_bind_prog_to_pipe.cpp

…

gl_separable_geometry_shader.cpp

…

gl_simple_triangle.cpp

…

gl_spirv_shader.cpp

…

gl_structured_buffer_nested.cpp

…

gl_test_linux.cpp

…

gl_test_win32.cpp

…

gl_test.cpp

…

gl_test.h

…

gl_unsized_ms_fbo_attachment.cpp

…

gl_vao_0.cpp

…