Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cypress production test runs with older Node.js 16 version

See original GitHub issue

Where to find the issue

.github/workflows/cypress-test-prod.yml

Describe the issue

The workflow “Cypress Test Production” .github/workflows/cypress-test-prod.yml runs using the Node.js version v16.13.0. This is not the Node.js 18 lts/hydrogen version used in the other workflows, build.yml and deploy-master.yml, on cwa-website.

Steps to reproduce

View the action logs https://github.com/corona-warn-app/cwa-website/actions/workflows/cypress-test-prod.yml

Suggestion

Currently there are no errors caused by using the older Node.js version v16.13.0 to check the production website. The workflow does not need to build the web. It only checks the existing published website.

The workflow “Cypress Test Production” .github/workflows/cypress-test-prod.yml uses the action cypress-io/github-action@v4 which is set up to use node16. There is a restriction in this action that means it is currently not possible to run it under Node.js 18. See issue https://github.com/cypress-io/github-action/issues/642.

For the moment I suggest no change, however the GitHub repository https://github.com/cypress-io/github-action has quite a backlog of issues and updates necessary. If these become a problem then it would be possible to replace the use of cypress-io/github-action@v4 by a direct call to Cypress (npx cypress), providing actions/setup-node and npm ci are run before the cypress call.

Issue Analytics

State:
Created 10 months ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

brianebelingcommented, Dec 6, 2022

Cool, thanks for monitoring it so extensively!

1reaction

MikeMcC399commented, Dec 5, 2022

@brianebeling

I think this is still relevant to an extend. Its not a pressing issue, but something we should monitor. Thank you for the headsup!

OK. I’m working in the https://github.com/cypress-io/github-action repository to try to clarify and I will update here. In the meantime, perhaps you could remove the https://github.com/corona-warn-app/cwa-website/labels/bug label which I accidently submitted under? It’s not really a bug if everything is working and the Cypress tests are passing. It’s more of a potential risk issue. You could add the https://github.com/corona-warn-app/cwa-website/labels/cypress label instead.