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

[CICD] e2e tests fail with "Error: Unable to deserialize cloned data due to invalid or unsupported version." #1145

Open
edwardfoyle opened this issue Mar 13, 2024 · 4 comments
Labels
flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling

Comments

@edwardfoyle
Copy link
Contributor

edwardfoyle commented Mar 13, 2024

Description

Example failure: https://github.com/aws-amplify/amplify-backend/actions/runs/8268357857/job/22621148134#step:8:1111

The stack trace is not very helpful

✖ /Users/runner/work/amplify-backend/amplify-backend/packages/integration-tests/lib/test-e2e/deployment.test.js (32599.221401ms)
  Error: Unable to deserialize cloned data due to invalid or unsupported version.
      at #proccessRawBuffer (node:internal/test_runner/runner:357:20)
      at FileTest.parseMessage (node:internal/test_runner/runner:293:28)
      at Socket.<anonymous> (node:internal/test_runner/runner:392:15)
      at Socket.emit (node:events:517:28)
      at addChunk (node:internal/streams/readable:368:12)
      at readableAddChunk (node:internal/streams/readable:341:9)
      at Readable.push (node:internal/streams/readable:278:10)
      at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)

ℹ tests 5
ℹ suites 5
ℹ pass 4
ℹ fail 1
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 780574.500193

✖ failing tests:

test at packages/integration-tests/lib/test-e2e/deployment.test.js:1:1
✖ /Users/runner/work/amplify-backend/amplify-backend/packages/integration-tests/lib/test-e2e/deployment.test.js (32599.221401ms)
  Error: Unable to deserialize cloned data due to invalid or unsupported version.
      at #proccessRawBuffer (node:internal/test_runner/runner:357:20)
      at FileTest.parseMessage (node:internal/test_runner/runner:293:28)
      at Socket.<anonymous> (node:internal/test_runner/runner:392:15)
      at Socket.emit (node:events:517:28)
      at addChunk (node:internal/streams/readable:368:12)
      at readableAddChunk (node:internal/streams/readable:341:9)
      at Readable.push (node:internal/streams/readable:278:10)
      at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
Error: Process completed with exit code 1.

This post looks like a similar issue: https://stackoverflow.com/questions/73034605/error-unable-to-deserialize-cloned-data-due-to-invalid-or-unsupported-version

It also looks like this is possibly (although unlikely) a bug in Node 18: https://answers.netlify.com/t/build-failing-after-upgrade-to-node-18/75774

@edwardfoyle edwardfoyle added testing Engineering label for issues related to tests or test tooling repo-infrastructure Engineering label for issues related to repo infrastructure flaky Engineering label for flaky tests labels Mar 13, 2024
@edwardfoyle
Copy link
Contributor Author

@edwardfoyle
Copy link
Contributor Author

Looks like this is the issue which only exists in node 20 and has been patched in node 21

@edwardfoyle
Copy link
Contributor Author

That may not fully explain things. We have some instances of this failure on tests running with node 18

@rtpascual
Copy link
Contributor

@josefaidt josefaidt added the tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky Engineering label for flaky tests repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
Projects
None yet
Development

No branches or pull requests

3 participants