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

Receiving Error When Attempting to Upload Test Replay #27712

Closed
kinson opened this issue Aug 30, 2023 · 10 comments
Closed

Receiving Error When Attempting to Upload Test Replay #27712

kinson opened this issue Aug 30, 2023 · 10 comments
Labels
v13.0.0 🐛 Issue present since 13.0.0

Comments

@kinson
Copy link

kinson commented Aug 30, 2023

Current behavior

I recently upgraded to 13.0.0 of Cypress and tried viewing a test replay in Cypress cloud. However, in the GitHub action run, I received the following error related to Test Replay:

  - Test Replay - Failed Capturing - [
  {
    "code": "invalid_type",
    "expected": "boolean",
    "received": "undefined",
    "path": [
      "response",
      "securityDetails",
      "encryptedClientHello"
    ],
    "message": "Required"
  }
]

Desired behavior

The desired behavior is for the test replay to upload and be viewable in Cypress cloud.

Test code to reproduce

I don't have a test file to share, this seems to be more of a GitHub <-> Cypress cloud issue unless I am misunderstanding.

Cypress Version

13.0.0

Node version

16

Operating System

ubuntu-latest (in GH Actions)

Debug Logs

No response

Other

No response

@cupcakepanda89
Copy link

I encountered the same issue with AWS Codebuild and following this trouble shoot below and they are all checked

  1. Confirm runs have been recorded to Cypress Cloud using Cypress v13 or later.
  2. Ensure tests were recorded using a Chromium-based browser (Chrome, Edge, Electron).
  3. Check that Test Replay is enabled in Cypress Cloud project settings.
  4. Review the standard output of the test run to ensure there was not an error capturing Test Replay. If you encounter an error capturing Test Replay, please open an issue so that we can investigate.

@javgarr
Copy link

javgarr commented Aug 31, 2023

Experiencing same issue on Chrome 80 (using cypress/browsers image)

====================================================================================================
  (Run Starting)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        13.0.0                                                                         │
  │ Browser:        Chrome 80 (headless)                                                           │
  │ Node Version:   v18.12.0 (/usr/local/bin/node)                                                 │
 (Uploading Cloud Artifacts)
  - Video - Nothing to upload 
  - Screenshot - Nothing to upload 
  - Test Replay - Failed Capturing - [
  {
    "code": "invalid_type",
    "expected": "array",
    "received": "undefined",
    "path": [
      "associatedCookies"
    ],
    "message": "Required"
  },
  {
    "code": "invalid_type",
    "expected": "object",
    "received": "undefined",
    "path": [
      "connectTiming"
    ],
    "message": "Required"
  }
]
────────────────────────────────────────────────────────────────────────────────────────────────────
                                                                                                    
  Running:  account/logout.feature                                                         (2 of 14)
  Estimated: 10 seconds
  Logout
    ✓ A user can logout and see the WWW homepage (8444ms)
  1 passing (9s)

Tests hang after this, cypress cloud timeouts. We are forced to rollback to Cypress 12 until this is fixed.

EDIT: Tests are hanging also on electron and chrome106 in all cases prior to uploading Cloud Artifacts.

@jennifer-shehane
Copy link
Member

If you’re encountering an error capturing Test Replay, please include the error code printed to the terminal output, we’ll follow up if more information is needed on our side to understand the reason for the error. I know we’re working on fixing some of these already.

@javgarr Can you open a separate issue regarding the run hanging please.

@jennifer-shehane jennifer-shehane added the v13.0.0 🐛 Issue present since 13.0.0 label Aug 31, 2023
@jennifer-shehane
Copy link
Member

We have a fix for this coming out in 13.1.0. We'll try to get this out today. After that release you'll need to upgrade to 13.1.0 to avoid these errors.

@jennifer-shehane
Copy link
Member

The code for this is done in #27709, but this has yet to be released.

@kinson
Copy link
Author

kinson commented Aug 31, 2023

Thanks for the update @jennifer-shehane ! I noticed that I was able to view a test replay this morning after another set of tests ran and it looks rad!

Once 13.1.0 is out I'll upgrade to it as well 🙌🏻

@kzs61
Copy link

kzs61 commented Oct 4, 2023

I'm having this issue with version 13.3.0 Verified everything @cupcakepanda89 suggested here

@jennifer-shehane
Copy link
Member

@kzs61 Could you open an issue with the exact error message you're seeing? DEBUG logs would be helpful too. This exact cause was fixed, so likely there is something specific with your run that we need to investigate. We're prioritizing these errors and will prioritize if you can get us the details. Thanks!

@kzs61
Copy link

kzs61 commented Oct 5, 2023

@kzs61 Could you open an issue with the exact error message you're seeing? DEBUG logs would be helpful too. This exact cause was fixed, so likely there is something specific with your run that we need to investigate. We're prioritizing these errors and will prioritize if you can get us the details. Thanks!

@jennifer-shehane It's 'GLIBC_2.29' not found (Alpine image latest version 3.18, node v16)

@jennifer-shehane
Copy link
Member

@kzs61 You can track the GLIBC error here: #27902 We have a fix that we hope to release soon for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v13.0.0 🐛 Issue present since 13.0.0
Projects
None yet
Development

No branches or pull requests

5 participants