Repository navigation
[CICD] e2e tests fail with "Error: Unable to deserialize cloned data due to invalid or unsupported version." #1145
Description
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
Activity
edwardfoyle commentedon Mar 14, 2024
This is happening more frequently: https://github.com/aws-amplify/amplify-backend/actions/runs/8273516781/job/22642099342#step:8:1131
edwardfoyle commentedon Mar 14, 2024
Looks like this is the issue which only exists in node 20 and has been patched in node 21
edwardfoyle commentedon Mar 14, 2024
That may not fully explain things. We have some instances of this failure on tests running with node 18
rtpascual commentedon Mar 18, 2024
Another instance of this error: https://github.com/aws-amplify/amplify-backend/actions/runs/8303242067/job/22756637640#step:8:826