Skip to content
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

Error: /lib64/libm.so.6: version `GLIBC_2.29' not found #3735

Closed
2 tasks done
ccks01 opened this issue Sep 28, 2023 · 5 comments
Closed
2 tasks done

Error: /lib64/libm.so.6: version `GLIBC_2.29' not found #3735

ccks01 opened this issue Sep 28, 2023 · 5 comments
Assignees
Labels
archived This issue has been locked. e2e-cypress-tests Cypress/E2E test step issue transferred This issue was transferred from another Amplify project usability

Comments

@ccks01
Copy link

ccks01 commented Sep 28, 2023

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

16

Amplify CLI Version

10.6.2

What operating system are you using?

Amazon Linux:2 default

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

no

Describe the bug

Can not use Cypress anymore. Update to 13.3.0. Gives error in console:

2023-09-28T07:42:15.506Z [INFO]: Error: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by /root/.cache/Cypress/13.3.0/Cypress/resources/app/packages/server/lib/modes/addon/addon-native.node)

Expected behavior

Can use Cypress in build pipeline

Reproduction steps

install Cypress 13.3.0
run Cypress in build pipeline

Project Identifier

No response

Log output

No response

Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@ccks01
Copy link
Author

ccks01 commented Sep 28, 2023

Going back to 12.17.4 it runs again

@ykethan
Copy link
Member

ykethan commented Sep 28, 2023

Hey @ccks01, thank you for reaching out. A similar issue on the Cypress repository is currently open here: cypress-io/cypress#27902.
I'm going to transfer this over to our hosting repository for better assistance 🙂.

@ykethan ykethan transferred this issue from aws-amplify/amplify-cli Sep 28, 2023
@ykethan ykethan added the transferred This issue was transferred from another Amplify project label Sep 28, 2023
@Jay2113 Jay2113 self-assigned this Oct 3, 2023
@Jay2113 Jay2113 added usability e2e-cypress-tests Cypress/E2E test step issue and removed pending-triage labels Oct 3, 2023
@Jay2113
Copy link
Contributor

Jay2113 commented Oct 3, 2023

Hi @ccks01 👋 , the Cypress team have released a fix for this issue as stated here: cypress-io/cypress#27920 (comment).

Thus, I am going to close this issue. Thanks!

@Jay2113 Jay2113 closed this as completed Oct 3, 2023
@github-actions
Copy link

github-actions bot commented Oct 3, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

@github-actions
Copy link

github-actions bot commented Oct 3, 2023

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Oct 3, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. e2e-cypress-tests Cypress/E2E test step issue transferred This issue was transferred from another Amplify project usability
Projects
None yet
Development

No branches or pull requests

3 participants