fix: serialize changedFiles passed to workers

[thymikee]

Summary

Serialize Set to Array in coverage and test workers.
Fixes #8084.

Test plan

@SimenB feel free to add a test, I need to run away from my computer at the moment.

[SimenB]

context not config, no?

[thymikee]

yea, how did that passed typecheck :o

[SimenB]

I think config is a superset of context

[leonfs]

Is there a date on when is this going to be released? Not being able to watch tests if coverage is enabled is quite a pain.

[SimenB]

Hopefully today

[arb]

I updated to 24.4.0 and am still having the issue described in #8084 and #8088.

npx: installed 1 in 1.147s

  System:
    OS: macOS 10.14.3
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 8.11.1 - ~/.nvm/versions/node/v8.11.1/bin/node
    Yarn: 1.9.4 - ~/.nvm/versions/node/v8.11.1/bin/yarn
    npm: 5.6.0 - ~/.nvm/versions/node/v8.11.1/bin/npm
  npmPackages:
    jest: 24.x.x => 24.4.0 

[SimenB]

Could you put together a reproduction?

[arb]

Same repo as #8088

https://github.com/arb/celebrate/tree/feature-ref

That branch, npm test locally fails with the same error. I've bumped to jest@24.4.0 and it's failing in the same way. I apologize it's not a small repo. I tried starting a new project with the same setup, but I couldn't get it to fail the same way.

[thymikee]

@arb it's a problem you your package manager. Try yarn or at least remove Jest references from package-lock.json.

Running:

yarn
yarn jest --changedSince=master
yarn jest --watch

works just fine.

[arb]

@thymikee removed all of package-lock.json and re-ran npm i; same problem. Removed package-lock.json and ran yarn jest --watch; same problem. Worth noting is that --changedSince=master did seem to work.

The (currently) two 👍on #8090 (comment) makes me think there are others who have tried the new version and are having the same problem even after the update. Are there any suggestions for how I can help resolve this issue?

[leonfs]

We have upgraded and it's working fine for us. Many thanks @SimenB !!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.