You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have 6 headless tests running on Chrome, Firefox and Edge for my Dev and Production. These all pass on my local environment.
On the Gitlab-CI all pass except for the Firefox Production test. From the debug logs I see an excessive number of
cypress:launcher firefox stdout: [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt +18ms
There are also logs like that in the passing Firefox Dev environment test but much less in number.
Could this be then causing my page not to load properly during the test? How can I access the Developer Tools after the Gitlab-CI test.
Below is an example of the logs:
The firefox test :
- npx cypress run --browser firefox --spec "cypress/integration/*"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have 6 headless tests running on Chrome, Firefox and Edge for my Dev and Production. These all pass on my local environment.
On the Gitlab-CI all pass except for the Firefox Production test. From the debug logs I see an excessive number of
cypress:launcher firefox stdout: [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt +18ms
There are also logs like that in the passing Firefox Dev environment test but much less in number.
Could this be then causing my page not to load properly during the test? How can I access the Developer Tools after the Gitlab-CI test.
Below is an example of the logs:
The firefox test :
- npx cypress run --browser firefox --spec "cypress/integration/*"
Cypress 8.3.0
image: cypress/browsers:node14.17.0-chrome91-ff89
Beta Was this translation helpful? Give feedback.
All reactions