"Attempted to initialize a Vulkan playground on macOS where Vulkan cannot be found. It can be installed via MoltenVK and make sure to install it globally so dlopen can find it.". This is on Linux. Something is deeply confused.

Wait, what is linux mac_unopt? Is it linux or mac?

"Attempted to initialize a Vulkan playground on macOS where Vulkan cannot be found. It can be installed via MoltenVK and make sure to install it globally so dlopen can find it.". This is on Linux. Something is deeply confused.

I suspect that this is just a failure to load vulkan and the error message is macos centric. Is impeller_unittests supposed to be running on linux with swiftshader? If so this can probably be fixed with the VK_ICD_FILENAMES environment variable set to swiftshader like we do on macos.

This isn't linux. I filed flutter/flutter#142010 to fix the confusingly named bot. I don't think this bot has Molten and the playgrounds aren't configured for SwiftShader. I'll just skip the tests in this configuration.

Wait, what is linux mac_unopt? Is it linux or mac?

Oh that's mac, if you click into the results like https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Engine%20Drone/648482/overview you can see it.

I don't know the right nomenclature but that is a linux bot dishing out tasks to mac bots.

Ok, attempting to run a playground on a host that doesn't support Vulkan even via Molten shouldn't be an error anymore. We can patch it later to work with SwiftShader but that is a heavier lift. I'll investigate the other validation error.

Ok, attempting to run a playground on a host that doesn't support Vulkan even via Molten shouldn't be an error anymore. We can patch it later to work with SwiftShader but that is a heavier lift.

Running with swiftshader should be an easy change. We are already doing it for the impeller_golden_tests executable. Check out run_tests.py and see where it is setting up VK_ICD_FILENAMES

Wilco on investigating running it with SwiftShader. The current validation error is pasted below. I think this one is real. Investigating a fix.

[ RUN      ] Play/RuntimeStageTest.CanCreatePipelineFromRuntimeStage/Vulkan
[INFO:capabilities_vk.cc(51)] Vulkan validations are enabled.
[FATAL:flutter/impeller/base/validation.cc(47)] Break on 'ImpellerValidationBreak' to inspect point of failure: 
--- Vulkan Debug Report  ----------------------------------------
|                Severity: Error
|                    Type: { Validation }
|                 ID Name: VUID-VkGraphicsPipelineCreateInfo-layout-07988
|               ID Number: 559874765
|       Queue Breadcrumbs: [NONE]
|  CMD Buffer Breadcrumbs: [NONE]
|         Related Objects: ShaderModule [2205620325320662] [Shader ink_sparkle_fragment_main], PipelineLayout [2208918860203993] [UNNAMED]
|                 Trigger: Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-layout-07988 ] Object 0: handle = 0x7d600000007d6, name = Shader ink_sparkle_fragment_main, type = VK_OBJECT_TYPE_SHADER_MODULE; Object 1: handle = 0x7d900000007d9, type = VK_OBJECT_TYPE_PIPELINE_LAYOUT; | MessageID = 0x215f02cd | vkCreateGraphicsPipelines(): pCreateInfos[0] Set 0 Binding 64 in shader (VK_SHADER_STAGE_FRAGMENT_BIT) uses descriptor slot (expected `VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER, VK_DESCRIPTOR_TYPE_UNIFORM_BUFFER_DYNAMIC, VK_DESCRIPTOR_TYPE_INLINE_UNIFORM_BLOCK`) but not declared in pipeline layout The Vulkan spec states: If a resource variables is declared in a shader, a descriptor slot in layout must match the shader stage (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-layout-07988)
-----------------------------------------------------------------

Oof. Thats just a single validation error. Theres loads more when I make the harness not tear down on validation error. https://gist.github.com/chinmaygarde/c2c4025fcf452a9ef67618c740b71425

I think @gaaclarke and I have fixed most of these validation errors. What are the remaining blockers?

Good to know. I'll rebase and check again to see if I get a clean run.