-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fails to POST DOM snapshot to CLI server: TypeError: Cannot read property 'end' of undefined
#367
Comments
This is also happening on our end, and has started about two days ago. We first thought that it could have been due to upgrading from We tried it with both Cypress 7.5.0 and 7.6.0. Any advice? |
Thanks for the issue! The most helpful thing would be logs from the test run ( |
I hope I am not doing anything wrong on my end, but the Command used:
|
On running with
|
Can we get a full log output? What @shalem-pravas provided was the closest (there's a real error there), but having full logs would help figure out what is causing the error. |
We are using |
|
These are the kind of logs I'm asking for (
I can only see that error (which matches what @shalem-pravas shared a snippet of) on Node 11.9.x or earlier:
Seems to strongly suggest it's a Node version issue (or the version of node being used has been altered maybe?). A reproduction would be really helpful since I can't get it to break with that error without going down to an unsupported version of Node. |
@Robdel12 sorry I cant share the code as it's a private repo, but here's the build gist
as per your request here's the node version:
and the cypress run command
|
@Robdel12 by the way, funny part is screenshots are being uploaded to percy, it's just the tests that are failing |
Having same issue with cypress 5.6.0 and node 14.16.0 |
A reproduction would be the most helpful, given I can't reproduce on Node 12+. Using the example app with Node 14.16.1: https://github.com/percy/example-percy-cypress/runs/2934658148?check_suite_focus=true Using the example app with Node 11.9.x fails with the error provided in this issue: https://github.com/percy/example-percy-cypress/runs/2934668779?check_suite_focus=true The error really seems to suggest it's an issue with the version of Node being used. I can't break it in the same way (yet?) & there's only been one log posted with an error stack trace, so I'm assuming everyone is hitting this error:
|
Published a new version of the CLI which will hard exit if it detects a version of Node that's not supported: https://github.com/percy/cli/releases/tag/v1.0.0-beta.57 Curious if that errors or not. If not, I'm keen to get a reproduction or more details on how to reproduce this issue 👀 |
|
here's my latest update
results :
all the test that fails has the same logs, then :
I've also noticed , it always fails on the same pages. hope this helps @Robdel12 . |
For me the number of failed tests is different. Sometimes it varies from 31 to 35. |
@aleksandrlat your issue isn't at all related -- looks like you have duplicate snapshot:
if the tests are retried, that won't work with Percy (for now, in the future we'll be updating the SDKs to handle retries percy/cli#281). |
@kaminskypavel hm, that's interesting. I don't think we're talking about the same error as the original issue. I'm going to rename this one to be about the Node error ( There aren't any other logs that provide a stack trace from Percy or anything? This is pretty generic and coming from Yarn 🤔
|
TypeError: Cannot read property 'end' of undefined
@Robdel12 I have more than 30 failing tests and others don't have this problem. And these tests have been working for ages without any changes on our side |
With the logs you provided, it's because |
Here is another test failure Do all tests fail because of this? But in the code |
On different CircleCI tab I see the same error coming from Cypress from all failing tests including that one about
|
for everyone having this issue, add the following line to cypress.json
this solves the problem. 🎉💃 |
Let's open another issue, the orignal issue here was addressed (#367 (comment)) These all have the same Cypress error, but any response that doesn't resolve from the CLI will have that Cypress error -- it's generic. See #371 |
Percy snapshot seems to be failing with the following error
CypressError:
cy.then()timed out after waiting
15000ms`.Your callback function returned a promise that never resolved.
The callback function was:
async () => {
if (Cypress.config('isInteractive') &&
!Cypress.config('enablePercyInteractiveMode')) {
return cylog('Disabled in interactive mode', {
details: 'use "cypress run" instead of "cypress open"',
name
});
}
}
https://on.cypress.io/then`
Code:
cy.visit('/') cy.url().should('include', '/auth/signup') cy.percySnapshot()
The text was updated successfully, but these errors were encountered: