This has been happening for a while locally, which makes the publishing pipeline annoying sometimes:
Assertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 176.
error Command failed with signal "SIGABRT".
Haven't experienced that since #197. Can be potentially fixed.
Run the integration tests multiple times, the issue is reproducible.
I'm facing the same issue now 馃 . I can't start regression tests
@marcosvega91, sorry to hear that. It usually helps to re-run the test(s). I know it's not ideal, but I don't know any technical details about this issue yet to resolve it. Most likely it's related to the test setup (WDS + Puppeteer). I like that setup, but I see some memory implications there.
unfortunately to it doesn't work even I rerun 馃槩 I'll try to find a different way
Could you please update me with the OS you are using? Maybe that could help us find the root cause of the issue. Also, does this happen when you run all the tests, or even a single test in isolation?
I have a mac with macOS Catalina. It is happening if I run a single test or all tests
regarding the issue I have read this. I have tried to update watchpack to a different version and now sometimes they work and sometimes not.
@marcosvega91 the workaround there worked, cheers!
Adding
"resolutions": {
"chokidar": "3.3.1"
}
to package.json causes warnings on the yarn install, but makes the tests work consistently.
That's a great find! Please, could you open a pull request with that custom resolution?
Sure, are you ok with it printing the warnings to the console?
yarn install v1.22.4
[1/4] 馃攳 Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "chokidar@^2.1.8"
warning Resolution field "[email protected]" is incompatible with requested version "chokidar@^2.1.8"
I wonder if there is a way to suppress them per/package
I'd carefully check if those warnings originate from development dependencies or production dependencies. It wouldn't be nice for anybody installing msw to experience those warnings. If they are for dev, then it's completely fine.
It's originating from watchpack that is a dependency of webpack so I think that we can proceed without a problem
Most helpful comment
@marcosvega91 the workaround there worked, cheers!
Adding
to
package.jsoncauses warnings on the yarn install, but makes the tests work consistently.