Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] GitHub + macOS + Node 14: All tests pass but process exits with code 134

See original GitHub issue

Context:

Playwright Version: 1.2.0
Operating System: macOS
Node version: 14
Browser: Webkit
Extra: Running as GitHub Action using microsoft/playwright-github-action v1.3.0

Running one project: e2e
PASS browser: chromium e2e tests/e2e/example.test.js
PASS browser: firefox e2e tests/e2e/example.test.js
PASS browser: webkit e2e tests/e2e/example.test.js
PASS browser: chromium e2e tests/e2e/vue.test.js
PASS browser: firefox e2e tests/e2e/vue.test.js
PASS browser: webkit e2e tests/e2e/vue.test.js

Test Suites: 6 passed, 6 of 2 total
Tests:       24 passed, 24 total
Snapshots:   0 total
Time:        21.526 s
Ran all test suites.
Assertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 178.
/Users/runner/work/_temp/241fae1a-1600-440c-9c4a-dc01208caa50.sh: line 1:  3699 Abort trap: 6
npm run test:jest-e2e -- -ci
##[error]Process completed with exit code 134.

Tests pass with all other os/node versions:

macOS + Node 10/12 (not 14)
Ubuntu + Node 10/12/14
Windows + Node 10/12/14

Issue Analytics

State:
Created 3 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

jhildenbiddlecommented, Jul 27, 2020

Thanks to @aslushnikov and @yury-s I was able to track down the issue. The linked issues provided by @yury-s convinced me that an outdated version of chokidar was likely the cause. I ran the following CLI command to determine if a dependency on an outdated version existed in our project:

npm ls chokidar

Sure enough, this was the result:

├── chokidar@3.4.1 
├─┬ live-server@1.2.1
  └── chokidar@2.1.8

Turns out live-server is still using chokidar v2. A live-server PR has been created to address the issue, but since that PR is now four months old with no sign of activity, we made the switch to browser-sync. Very happy to report that all tests pass without issue now.

Thanks again for your help. The linked issues were critical in identifying the problem. Very much appreciated!

0reactions

jhildenbiddlecommented, Jul 24, 2020

@yury-s –

Turns out that setting runInProcess to true for jest-image-snapshot solves the issue so I recreated an issue there: https://github.com/americanexpress/jest-image-snapshot/issues/231.

For clarification, I believe the issue is macOS- and/or GitHub-specific, not Webkit-specific. All tests pass without issue locally on macOS and on both Ubuntu and Windows using GitHub Actions.