-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)" on GitHub Docker #27741
Comments
The issue is also reproducible without GitHub Actions running a Cypress Docker Using Xvfbdocker run -it -v $PWD:/e2e -w /e2e --entrypoint cypress cypress/included:latest run --project . --e2e the same errors are output as when running under GitHub Actions:
Using WSL2/WSLgMicrosoft WSL2 with Windows Subsystem for Linux GUI (WSLg). Using the WSLg X11 server instead of Xvfb no errors are output: docker run -it -v /tmp/.X11-unix:/tmp/.X11-unix -v /mnt/wslg:/mnt/wslg -e DISPLAY=$DISPLAY -e WAYLAND_DISPLAY=$WAYLAND_DISPLAY -e XDG_RUNTIME_DIR=$XDG_RUNTIME_DIR -e PULSE_SERVER=$PULSE_SERVER -v $PWD:/e2e -w /e2e --entrypoint cypress cypress/included:latest run --project . --e2e |
This issue is no longer reproducible in Cypress 13.2.0. According to the Changelog:
Presumably this is the reason for the error message no longer appearing. |
to fix the new weird issue on the CI pipeline: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) cypress-io/cypress#27741
in cypress 13.6.2
|
Are you running in a Cypress Docker container? |
no @MikeMcC399 i did not use Cypress Docker, suddenly it produce this error, how can i check docker by cmd? |
The issue here is only concerning a Cypress Docker environment and this problem is already resolved, which is why this issue is closed. I have also seen the error when I run Cypress in Ubuntu under VMware Workstation. In my experience you can ignore the error.
If you think that this is a Cypress bug and you want to report it, then I suggest you open a new issue and provide all the requested information, such as your operating system, debug logs, etc. Cypress Docker is available for instance in GitHub Actions - see Using Docker Images. You can also install it locally (see Docker getting started). You can also get assistance from the Cypress technical community on Discord |
Current behavior
When Cypress is run in a Cypress Docker container cypress/browsers or cypress/included running under a GitHub-hosted runner then the following errors are logged:
Both the above two error log lines may be classed as "garbage warnings".
This issue is concerned only with the
libva
error.The
ERROR:gpu_memory_buffer_support_x11.cc(44) / dri3 extension not supported
error is separately covered in the issue #25357.Desired behavior
No
libva error
should be output in a GitHub-hosted runner using a Cypress Docker container.GitHub-hosted runners do not provide a GPU (Graphics Processing Unit). libva is an implementation for VA-API (Video Acceleration API) and where there is no GPU, there can be no video acceleration.
If Cypress is invoking Xvfb (X virtual framebuffer) because there is no X11 server available, then it should not expect to have video acceleration available. If possible, it should disable attempting to use video acceleration and if this is not possible then related
libva
errors should be ignored and suppressed.Note also that the workaround of adding the following environment variable has no effect on the
libva
error although it does prevent thedri3
error appearing for browsers other than Electron:Test code to reproduce
Simplest example to illustrate issue
Full workflow examples on:
cypress:*,xvfb,xvfb-process
enabledCypress Version
13.1.0
Node version
20.5.0
Operating System
Ubuntu 22.04
Debug Logs
Full debug logs
see GitHub workflows above
Other
Related issues
cy.request()
timed out waiting30000ms
for a response from your server #23326The text was updated successfully, but these errors were encountered: