Unexpected response from worker

[iGitScor]

Hi,

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
A bunch of test fail after several passed test

If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can yarn install and yarn test.

Users/sebastien/project/node_modules/jest-worker/build/worker.js:169
        throw new TypeError('Unexpected response from worker: ' + response[0]);
        ^

TypeError: Unexpected response from worker: undefined
    at _receive (/Users/sebastien/project/node_modules/jest-worker/build/worker.js:169:15)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at process.nextTick (internal/child_process.js:744:12)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
error Command failed with exit code 1.

I don't know how I can give you more information, but please ask 🙏

What is the expected behavior?

Run all the tests

Please provide your exact Jest configuration

Run npx envinfo --preset jest in your project directory and paste the
results here

  System:
    OS: macOS Sierra 10.12.6
    CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 6.9.5
    Yarn: 1.3.2
    npm: 4.6.1
  npmPackages:
    jest:
      wanted: ^22.4.0
      installed: 22.4.3

[SimenB]

We need a reproduction to be able to debug this

[iGitScor]

Except if I give you the right to the private source, I don't know how to give you a step-by-step reproduction (or I'd have a clue to debug).

Is there specific case when this error is triggered ?

[SimenB]

I have never seen the error before.

/cc @mjesun

[iGitScor]

More info, I don't know if it's useful

• Config in package.json

  "jest": {
    "collectCoverageFrom": [
      "server/**/*.js",
      "!**/mocks/**"
    ],
    "setupFiles": [
      "./setup.js"
    ],
    "setupTestFrameworkScriptFile": "./node_modules/jest-xml-matcher/index.js",
    "testMatch": [
      "<rootDir>/__tests__/**/*.spec.js?(x)",
      "<rootDir>/__tests__/**/test_*.js?(x)"
    ],
    "transform": {
      ".(js)": "<rootDir>/node_modules/babel-jest"
    }
  }

• Content of setup.js

import 'jest-googleapi-mock';

[mjesun]

Never seen this error as well; and AFAIK it's the first report we have. The config looks pretty OK too. I'd recommend to take a copy of the repo and start trimming files and other stuff until you have a test case you can share with us.

Based on the throw you are experiencing, it looks like an unmocked process.send call is being made from a test; could that be the case?

[iGitScor]

Wow, awesome! That's exactly the point. We use pmx which wasn't mocked and which calls process.send function.
Do you now if there is a known mock for process.send ?

[mjesun]

To be fair, I don't think that's something you should be addressing. jest-environment-node creates, via jest-util, a deep copy of the process object, to be used as a fake/mock process object inside the context. But our deepCopy implementation just references functions, so you end up with the real process.send.

The reason why no one noticed it is because this API is not usually used, and in our case (which we use), we have to mock process.send to assert that jest-worker does what is expected. 😄

I've set up #5904 as a fix for the issue, but I'm not sure when it will be merged/released. We're already in a jest@23 alpha release, and it's easter holidays. But I'll make my best to have something shipped soon. 🙂

[iGitScor]

Thank you @mjesun 🙂

[calidion]

how to mock? i have the same problem.

[mjesun]

@calidion the function should be mocked already, as per #5904

[calidion]

@mjesun I still encountered this error.

[SimenB]

You'll need to install jest@beta