Various logging clean-up / upgrades

[aruby-blackberry]

See commits for desciption.

At default logging level, can now see the ExternalMemoryMode logged at INFO:

...
 [vk_common_operations.cpp(1289)] Selecting Vulkan device: V3D 7.1.7.0, Version: 1.3.311
 [vk_common_operations.cpp(1293)] Using Vulkan externalMemoryMode: QnxScreenBuffer for VkEmulation
 [vk_common_operations.cpp(260)] Warning: using non-cached HOST_VISIBLE type for staging memory
 [vk_common_operations.cpp(1586)] Initializing VkEmulation features:
[vk_common_operations.cpp(1587)]     glInteropSupported: false
 [vk_common_operations.cpp(1589)]     useDeferredCommands: true
...

[aruby-blackberry]

@jmacnak please merge.

[jmacnak]

@aruby-blackberry : @gurchetansingh might have found the magic config option to allow collaborators to kick off kokoro as well. If you can, perhaps try force pushing your branch in like an hour or so and we'll see if it kicks off automatically

[aruby-blackberry]

@aruby-blackberry : @gurchetansingh might have found the magic config option to allow collaborators to kick off kokoro as well. If you can, perhaps try force pushing your branch in like an hour or so and we'll see if it kicks off automatically

Ahh, thanks for doing some searching! I will try that in about an hour then 👍

[gurchetansingh]

You can also check the right side and try adding "kokoro run" label as well.

[gurchetansingh]

@jmacnak hmm looks like the @GoogleGfxstreamTesterBot is removing kokoro-run labels.

[aruby-blackberry]

@jmacnak hmm looks like the @GoogleGfxstreamTesterBot is removing kokoro-run labels.

@gurchetansingh actually I think this fine; the kokoro run has now started, so that's good!

[jmacnak]

Yeah, it removes the label once it starts running.