github-action: Action stuck at Warning: vkCreateInstance: Found no drivers!

We’re having runs on PRs with this action get stuck with

Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)

for hours.

It looks like once this error occurs, the action keeps running indefinitely until it will be terminated by GitHub.

See for example:

This started at 2024-02-28T18:50Z with https://github.com/envelope-zero/frontend/actions/runs/8085573515?pr=1550.

I did some research, but could not find anything for this error related to cypress so far.

About this issue

Original URL
State: closed
Created 4 months ago
Comments: 15

Commits related to this issue

test: move to Electron for e2e tests To have a shot at fixing https://github.com/cypress-io/github-action/issues/1136, we'll test with Electron — committed to envelope-zero/frontend by morremeyer 4 months ago
Downgrade to Cypress 13.6.4 because of https://github.com/cypress-io/github-action/issues/1136 — committed to Modern-MISP/frontend by feathecutie 4 months ago

Most upvoted comments

@roshnimridha04

Is there a plan to resolve this issue in future release of cypress as downgrading version to 13.6.4 works?

There is an open issue https://github.com/cypress-io/cypress/issues/29085 in the Cypress repo for this which you can follow. It’s not tracked in the github-action repo, since it is not a github-action bug. I suspect it may need Cypress to update the version of Electron it uses, but there is no confirmation of that theory at this time.

MikeMcC399 on Mar 27, 2024

@marcdix

I downgraded to 13.6.4 as you suggested and the error is gone.

Many thanks for your feedback! I passed that on to other users to try out as well.

MikeMcC399 on Mar 7, 2024

@MikeMcC399 I just googled for the error as I got it when running after updating Cypress to 13.6.6. I downgraded to 13.6.4 as you suggested and the error is gone. Hope this helps to identify the culprit. Thanks for everyones efforts.

marcdix on Mar 7, 2024

@sbrawner

Thanks for contributing your experience too! To test if this might be related to the Electron upgrade in cypress@13.6.5 from 25.8.4 to 27.1.3 you might like to try reverting to cypress@13.6.4.

MikeMcC399 on Mar 6, 2024

@morremeyer

Many thanks for your confirmation! Hopefully it will soon become clear what is causing this issue!

No, GitHub Actions does not use Docker in any hidden way., only if it is explicitly configured, for instance like the following in a workflow:
    container:
      image: cypress/browsers:latest
      options: --user 1001

I am using it in docker/kube and am having this exact issue. Backing down a version to see if it still occurs.

sbrawner on Mar 6, 2024

Since this posed the danger of leading me to the realm of “understanding display drivers”, which I do not have desire to explore, I decided to see what happens if I switch the tests to Electron.

Doing so did not get rid of the error message, as can be seen in https://github.com/envelope-zero/frontend/actions/runs/8124771638/job/22206650558?pr=1576, where it occurs once

However, the run does not get stuck when this error pops up.

I’m going to count this as a win. Thanks @MikeMcC399 for the poke in the right direction!

morremeyer on Mar 2, 2024

@MikeMcC399 Thanks for the pointers! I’ll dig into this and document any findings here in case anyone runs into it in the future.

morremeyer on Mar 2, 2024