"Percy agent is not running" in Cypress, 0 snapshots taken

[callumacrae]

Potentially related to #61, but I think it is a different issue.

I'm running my tests inside the percy agent:

[percy] created build #5: https://percy.io/SamKnows/client-dashboard/builds/1872425
[percy] percy has started.

In my tests, I have a cy.percySnapshot(), but it leads to the following output:

Then when the agent quits:

[percy] stopping percy...
[percy] waiting for 0 snapshots to complete...
[percy] done.

What's this about? node is definitely installed!

Disabling Cypress web security didn't help.

[Robdel12]

Hey Callum! This looks to be an issue I've been seeing with cy.exec. They use execa under the hood and it doesn't respect your systems $PATH. That error is basically saying it couldn't find node on your system because it's looking in one specific place. Related issue: sindresorhus/execa#153

We use cy.exec to run the health check so we can ensure our node server is open and ready to accept the snapshot POSTs: https://github.com/percy/percy-cypress/blob/master/lib/index.ts#L12-L17

So, the fix here would be to symlink your systems node to where execa is expecting to find it:

$  sudo ln -s $(which node) /usr/bin/node

[callumacrae]

Ended up using /usr/local/bin/node instead because El Capitan doesn't let you modify /usr/bin, but that worked!

Thank you :)