Skip to content
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 when running cypress using firefox cypress/browsers:node16.14.2-slim-chrome103-ff102 #730

Closed
Tigatok opened this issue Aug 12, 2022 · 4 comments

Comments

@Tigatok
Copy link

Tigatok commented Aug 12, 2022

As the title suggests, I am running into an issue in my gitlab pipeline. I am using the following image: cypress/browsers:node16.14.2-slim-chrome103-ff102

as it supports node 16 and ff 102, which most accurately reflects my local environment.

Running with the command like so: - $(npm bin)/cypress run --config baseUrl=$BASEURL --spec "cypress/integration/*,cypress/integration/**/*" --browser firefox

And the following returns:

[STARTED] Task without title.
[SUCCESS] Task without title.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[498:0812/004913.111233:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
====================================================================================================
  (Run Starting)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        10.4.0                                                                         │
  │ Browser:        Firefox 102 (headless)                                                         │
  │ Node Version:   v16.14.2 (/usr/local/bin/node)                                                 │
  │ Specs:          13 found (redacted.spec.js, redacted.spec.js, │
  │                 redacted.spec.js, redacted.spec.js, redacted.spec.js, │
  │                 redacted.spec.js, redacted.spec.js, redacted.spec.j │
  │                 s, redacted...)                                                    │
  │ Searched:       cypress/integration/*, cypress/integration/**/*                                │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────────────────────────
                                                                                                    
  Running:  redacted.spec.js                                                 (1 of 13)
Timed out waiting for the browser to connect. Retrying...
Timed out waiting for the browser to connect. Retrying again...
The browser never connected. Something is wrong. The tests cannot run. Aborting...
The browser never connected. Something is wrong. The tests cannot run. Aborting...
The automation client disconnected. Cannot continue running tests.
Warning: We failed processing this video.
This error will not alter the exit code.
TimeoutError: operation timed out
    at afterTimeout (/root/.cache/Cypress/10.4.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:46:19)
    at Timeout.timeoutTimeout [as _onTimeout] (/root/.cache/Cypress/10.4.0/Cypress/resources/app/packages/server/node_modules/bluebird/js/release/timers.js:[76](redacted/-/jobs/1325874#L76):13)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

I looked around but not much seems to be showing up for others. Any ideas how to progress?

@vai0
Copy link

vai0 commented Dec 1, 2022

related: #747

@gunslingor
Copy link

Same, we haven't run our cypress tests in 6 months due to it.

@MikeMcC399
Copy link
Collaborator

@gunslingor

Same, we haven't run our cypress tests in 6 months due to it.

Node.js 16 has reached end-of-life.

  • Are you able to try with a newer Cypress Docker version?
  • Are you also running in GitLab?
  • Which version of Cypress are you using?

@MikeMcC399
Copy link
Collaborator

Closing due to inactivity.

@MikeMcC399 MikeMcC399 closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants