Percy server fails to respond with Cypress open
See original GitHub issuei have a new gatsby project, setup with cypress and percy-cypress, where i’m experiencing some crashing that i’m trying to narrow down. you can find a reproduction repository here.
to reproduce:
- start the gatsby site:
npm run develop
- in a new tab:
./node_modules/.bin/cypress run
(this works)./node_modules/.bin/cypress open
-> run tests -> crash
specifically disabling percy doesn’t seem to work either:
- start the gatsby site:
npm run develop
- in a new tab:
PERCY_ENABLE=false ./node_modules/.bin/cypress open
-> run tests -> crash
my initial thought was the percy server must be running no matter what, however if you then:
- start the gatsby site:
npm run develop
- in a new tab:
percy exec -- ./node_modules/.bin/cypress open
-> run tests- i see as output:
[percy] Skipping visual tests - Missing Percy token
[percy] Running "./node_modules/.bin/cypress open"
i still experience a crash. additionally, supplying a token doesn’t help either. while i don’t experience a crash in this particular scenario, i don’t my my team uploading snapshots running tests locally. i haven’t yet been able to disable percy for local development, with PERCY_BRANCH=local
or PERCY_ENABLE=false
. and fwiw, i’m using a Mac, on BigSur, version 11.2.3
.
let me know if you need more information. thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (6 by maintainers)
Top GitHub Comments
Thanks @MarosPistej for the workaround, it worked for me as well!
This was my crash error message, I put it here, so others may find the workaround easier
to my issue #320 which is most likely same as this one worked also modifying
cypress/support/index.js
file and include code bellowthis works even with Cypress
7.1.0
in fact calling
isPercyEnabled()
anytime but before invokingcy.percySnapshot()
work…