MikeMcC399
commented
7 months ago @TestIsTest001
If your own CI workflow is not being blocked, then you can ignore this error it seems.
Closed Rajesh-Kodandam closed 7 months ago
MikeMcC399
commented
7 months ago @TestIsTest001
If your own CI workflow is not being blocked, then you can ignore this error it seems.
chlorophant
commented
7 months ago This issue was breaking one of my pipelines.
yktoo
commented
7 months ago With DEBUG turned on, the Cypress process gets stuck indefinitely with:
MikeMcC399
commented
7 months ago @yktoo
In the tests that @roadSurfer ran, he found that if you run Cypress long enough you will get the Vulkan error, so I suspect in your case also that it might be overlaid over some other issue. If you go back in your log file before it shows just the process_profiler outputs repeating can you identify the last thing that Cypress did and maybe look at whether anything there looks suspicious?
yktoo
commented
7 months ago @MikeMcC399 I think you're right. Downgrading to 13.6.4 removed the warning but didn't fix the pipeline getting stuck. So apparently it's a different bug.
It's really hard to say what triggers the freeze because it's flaky: sometimes it gets stuck on a certain test, sometimes goes on. The only thing that is more or less certain, is that it only seems happen in tests that test an application running inside an iframe.
TestIsTest001
commented
7 months ago Hello,
Have the cypress team been able to replicate the issue please?
Thank you
chlorophant
commented
7 months ago For me I was getting the error when starting cypress in my pipeline. It would cause the tests to not run, and fail the suite. The only way I could get rid of it was to roll back cypress version. I believe it's a recent regression from within the last few weeks.
MikeMcC399
commented
7 months ago @chlorophant
The only way I could get rid of it was to roll back cypress version. I believe it's a recent regression from within the last few weeks.
Which Cypress version did you roll back to?
pearlberry
commented
7 months ago I am running into this issue on Cypress v13.6.6, running cypress in google cloudbuild. The issue also exists on v13.7.1.
│ Cypress: 13.6.6 │ │ Browser: Chrome 106 (headless) │ │ Node Version: v18.15.0 (/usr/local/bin/node) │ │ Specs: 39 found (engineering/admin.spec.js, engineering/api.spec.js, engineering/chec │ │ kout.spec.js, engineering/collaboration.spec.js, engineering/copy-deck.spec.js │ │ , engineering/enterprise.spec.js, engineering/folders.spec.js, engineering/inv │ │ ite.spec.js, engineerin...) │ │ Searched: integration/engineering/.spec.js, integration/qa/.spec.js, integration/templ │ │ ates/*.spec.js │ │ Params: Tag: false, Group: false, Parallel: true |
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)
It is not specific to any one test, happens across many different specs 🙁
pearlberry
commented
7 months ago It's really hard to say what triggers the freeze because it's flaky: sometimes it gets stuck on a certain test, sometimes goes on. The only thing that is more or less certain, is that it only seems happen in tests that test an application running inside an iframe.
This is true to my experience as well, however it does not happen 100% of the time even in tests interacting with iframes. It is intermittent/inconsistent between multiple runs of the same test.
CloneOfAlex
commented
7 months ago I am seeing this non stop for the past (at least) 3 weeks
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)PS C:\Workspace\cypress-tests\UITest> npx cypress --version
Cypress package version: 13.7.1
Cypress binary version: 13.7.1
Electron version: 27.1.3
Bundled Node version:
18.17.1
mahadeer
commented
7 months ago Facing the same issue on GitLab Pipeline. Need to get this resolved.
CloneOfAlex
commented
7 months ago The solution to fix it is simple - Downgrade Cypress to build: 13.3.3 !!!!!!!!!!!!!!!!!
TestIsTest001
commented
7 months ago Thats not really a solution..Not everyone can downgrade..We were facing this issue https://github.com/cypress-io/cypress/issues/5016 and it got fixed in 13.7.0..All versions below 13.7.0 are giving us the screenshot timeout error. My team have been using cypress version 12.14.0 for months and it would be really great to use a recent cypress version.
Yuri-Lima
commented
7 months ago Ok, after read all the comments. I cannot see a real solution yet. So i just wanna provide more data, because i am facing the issue.
I am using the cypress/factory:3.5.2
Below is my DockerFile, as you can see some few commented lines i was trying to install some few thing related to vulkan, but no success. Runner Team City but fisrt i am running in my local enviroment.
All test are in containers.
# Define other ARGs and perform additional setup here
ARG NODE_VERSION='18.19.1'
ARG YARN_VERSION='1.22.19'
ARG CYPRESS_VERSION='13.6.6'
# ARG CYPRESS_CACHE_FOLDER='~/.cache/Cypress'
ARG CHROME_VERSION='113.0.5672.92-1'
# ARG FIREFOX_VERSION='113.0'
# ARG EDGE_VERSION='113.0.1774.42-1'
FROM cypress/factory:3.5.2
# Install required system packages
RUN apt-get update && apt-get install -y \
libgtk2.0-0 \
libgtk-3-0 \
libgbm-dev \
libnotify-dev \
libnss3 \
libxss1 \
libasound2 \
libxtst6 \
xauth \
xvfb \
curl \
libgconf-2-4
# vulkan-tools \
# mesa-vulkan-drivers
# Ensure that the Vulkan ICD loader is properly set up
# ENV VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json:/usr/share/vulkan/icd.d/intel_icd.x86_64.json
# Install jq binary
RUN curl -Lo /usr/local/bin/jq https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64
# Make the jq binary executable
RUN chmod +x /usr/local/bin/jq
WORKDIR /opt/e2e
RUN npm cache clean --force
# Copy entrypoint script
COPY entrypoint-e2e.sh /opt/e2e/entrypoint-e2e.sh
# Grant executable permissions to entrypoint script
RUN chmod +x /opt/e2e/entrypoint-e2e.sh
COPY packages/ui-e2e/cypress.env.json /opt/e2e
COPY packages/ui-e2e/cypress.config.ts /opt/e2e
COPY packages/ui-e2e/cypress/ /opt/e2e/cypress
COPY packages/ui-e2e/tsconfig.json /opt/e2e/tsconfig.json
COPY packages/ui-e2e/package.json /opt/e2e/package.json
# Create the directory if it doesn't exist
# RUN mkdir -p packages/phoenix-ui-e2e
# Append data to cypress.env.json file
# RUN echo ', {"ENV": "E2E" }' >> packages/phoenix-ui-e2e/cypress.env.json
RUN yarn install --frozen-lockfileAs you can see that warning it seems to be literally random, sometime it happen in different stages of the test.
Even in Chrome it shows same warn
Running the Containers Locally in my Cloud Vps 8 VCPU 16 GB RAM - Ubuntu 22.04 Everything works as normal no failures!
This image is from Team City
cacieprins
commented
7 months ago Everyone, thank you for your contributions to this thread.
This warning is present when Cypress is run in a Docker container whose host does not have a GPU. A similar warning is present when Cypress is run on a machine that does not have a GPU. These warnings are coming from the primary Electron process that Cypress spawns, and not from any of the browsers launched by Cypress. These warnings should not be causing tests to fail or hang, as evidenced by example reproductions that have a fully passing test suite despite the warnings being present.
We will be suppressing this warning in a similar manner to other benign Electron warnings.
If a minimal reproduction is made available that proves failure due to this warning, we will re-assess.
Thank you!
TestIsTest001
commented
7 months ago When can we expect a release pls? thanks
jennifer-shehane
commented
7 months ago There is a pre-release binary including the fix above, if anyone is interested in trying it out instructions and the binary are here: https://github.com/cypress-io/cypress/commit/96b14c3e1762a253aac0d0413a2b3b5c1ee4d954#commitcomment-140832299
This will be included in our next release.
cypress-bot[bot]
commented
7 months ago Released in 13.7.3.
This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v13.7.3, please open a new issue.
Current behavior
Jenkis e2e tests are failing due to Vulkan
Cypress Version
13.6.6
Node version
20.11.0
Operating System
macOS Sonoma 14.3.1
Debug Logs
No response
Other
No response