Version
24.10.0
Platform
Subsystem
node:test
What steps will reproduce the bug?
While trying to migrate appium tests from mocha to the native test runner I face a weird exception, coming from the test runner itself:
type: 'test'
location: '/home/runner/work/appium/appium/packages/images-plugin/build/test/e2e/plugin.e2e.spec.js:1:1'
failureType: 'uncaughtException'
error: 'Unable to deserialize cloned data due to invalid or unsupported version.'
code: 'ERR_TEST_FAILURE'
stack: |-
#processRawBuffer (node:internal/test_runner/runner:354:20)
FileTest.parseMessage (node:internal/test_runner/runner:290:27)
Socket. (node:internal/test_runner/runner:400:15)
Socket.emit (node:events:519:28)
addChunk (node:internal/streams/readable:561:12)
readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
Readable.push (node:internal/streams/readable:392:5)
Pipe.onStreamRead (node:internal/stream_base_commons:189:23)
This exception is always reproducible in the CI env. In local env (macOS) it may go away after several retries, but then returns, which makes it intermittent.
To repro it locally:
git clone https://github.com/appium/appium.git
git checkout 1392fc7fb123745db4ed91644cefede5cf5cec8b
npm run build
cd packages/images-plugin
npm run test:e2e
How often does it reproduce? Is there a required condition?
Always reproduces in CI, randomly reproduces in local env
What is the expected behavior? Why is that the expected behavior?
I expect the test to pass, or at least provide a meaningful stack trace, so I can trace and fix the original issue if it's in my code.
What do you see instead?
https://github.com/appium/appium/actions/runs/27947241178/job/82695020982?pr=22415
Additional information
The PR address: appium/appium#22415
Failing job example: https://github.com/appium/appium/actions/runs/27947241178/job/82695020982?
Version
24.10.0
Platform
Subsystem
node:test
What steps will reproduce the bug?
While trying to migrate appium tests from mocha to the native test runner I face a weird exception, coming from the test runner itself:
This exception is always reproducible in the CI env. In local env (macOS) it may go away after several retries, but then returns, which makes it intermittent.
To repro it locally:
How often does it reproduce? Is there a required condition?
Always reproduces in CI, randomly reproduces in local env
What is the expected behavior? Why is that the expected behavior?
I expect the test to pass, or at least provide a meaningful stack trace, so I can trace and fix the original issue if it's in my code.
What do you see instead?
https://github.com/appium/appium/actions/runs/27947241178/job/82695020982?pr=22415
Additional information
The PR address: appium/appium#22415
Failing job example: https://github.com/appium/appium/actions/runs/27947241178/job/82695020982?