Assertion failed : (0) at the end of karma execution #3511

matthintosh · 2020-05-15T13:47:11Z

Issue

Hello, I using Karma + Webpack for running my unit tests and karma always display an error after testing and just before closing Chrome (or ChromeHeadless).

Error

The error is :
Assertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 187.
[1] 18461 abort npm run test-debug

Below a copy of my terminal
TOTAL: 87 SUCCESS 15 05 2020 15:35:04.564:DEBUG [karma-server]: Run complete, exiting. 15 05 2020 15:35:04.564:DEBUG [launcher]: Disconnecting all browsers 15 05 2020 15:35:04.564:DEBUG [launcher]: BEING_FORCE_KILLED -> BEING_FORCE_KILLED Assertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 187. [1] 18552 abort npm run test-debug

Software and hardware

The issue still appear on :

local environment (mac os Catalina 10.15.4) running the npm script
local environment running the maven script (java project+react) to build the entire project. Maven will failed because of the issue
gitlab CI running the maven script (linux server)

Karma config

Below my karma config :
`module.exports = function (config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '../../../',

    // frameworks to use
    // available frameworks: https://npmjs.org/browse/keyword/karma-adapter
    frameworks: ['requirejs', 'jasmine'],

    // list of files / patterns to load in the browser
    files: [
        //Static resources
        tests + 'test-main.js', // Will load ebxUI bundles..

        //Unit test here
        {pattern: tests + 'src/**/*.tsx', included: false},
        {pattern: tests + 'src/**/*.ts', included: false},

        //EBX lib
        {pattern: ebxUI + "js/**/*", included: false},

        {pattern: libTest + "/**/*", included: false}

    ],

    // list of files to exclude
    exclude: [],

    // // Redirect access to resources
    // proxies: {
    //   '/images/': 'http://localhost:11180/ebx-ui/images/'
    // },

    // preprocess matching files before serving them to the browser
    // available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
    preprocessors: {
        //TODO coverage is not useful currently, try to do like : https://github.com/mcliment/typescript-karma-webpack-coverage-sample
        'project-folder/src/test/src/react/**/*.ts*': ['webpack'],
    },

    webpack: webpackConfig,

    // test results reporter to use
    // possible values: 'dots', 'progress'
    // available reporters: https://npmjs.org/browse/keyword/karma-reporter
    reporters: ['progress', 'coverage'],

    // optionally, configure the reporter
    coverageReporter: {
        type: 'html',
        dir: tests + 'coverage/'
    },

    // web server port
    port: 9876,

    // enable / disable colors in the output (reporters and logs)
    colors: true,

    // level of logging
    // possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
    logLevel: config.LOG_INFO,

    // enable / disable watching file and executing tests whenever any file changes
    autoWatch: false,

    // start these browsers
    // available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
    browsers: ['Chrome',"ChromeCustom"],

    // Continuous Integration mode
    // if true, Karma captures browsers, runs the tests and exits
    singleRun: false,

    // Concurrency level
    // how many browser should be started simultaneous
    concurrency: "Infinity",

    // Prevent karma to crash for empty
    // tests
    failOnEmptyTestSuite: false,

    // Set karma timeout
    browserNoActivityTimeout : 60000,
    processKillTimeout:30000,



    // Custom karma execution for CI
    customLaunchers: {
        ChromeCustom: {
            base: 'ChromeHeadless',
            // We must disable the Chrome sandbox when running Chrome inside Docker (Chrome's sandbox needs
            // more permissions than Docker allows by default)
            flags: isDocker ? ['--no-sandbox'] : []
        }
    }
})`

package.json file

More info

Sometimes (it's rare) the script end well and I don't have the issue.

NPM and node version

node: v12.16.3
npm:6.14.4

The text was updated successfully, but these errors were encountered:

devoto13 · 2020-05-15T17:21:13Z

It is not coming from Karma package, but rather from libuv (the binary used by Node itself). Can you try on the Node 12.15.0 (as libuv was updated in 12.16.0) and also on latest Node?

From the code it looks like Node attempts to close some resource of an unknown type and hence this assertion. This sounds either like Karma is doing something utterly wrong (not sure how it is possible though) or there is a bug in Node itself.

If you can provide a minimal Karma project which reliably produces this error this should help with debugging and potentially reporting a problem upstream.

devoto13 · 2020-05-15T17:45:32Z

Looks like the culprit is webpack/webpack#10037.

tl;dr Webpack is stuck with the older versions of fsevents/chokidar and maintainers of fsevents are unwilling to invest a lot of time into back-porting the fixes from the latest version (fsevents/fsevents#314). So either accept this issue or stay on older versions of Node where it is not present.

Karma has already upgraded to the latest fsevents and chokidar, so there is nothing for Karma core to fix here.

matthintosh · 2020-05-15T18:19:28Z

Thank you for your reply, I will test it and let you know (maybe test with a beta version of webpack5 or some resolutions to force latest version of chokidar/fsevents).

devoto13 · 2020-05-15T18:27:18Z

Actually this also may be caused by Karma. fsevents/fsevents#314 (comment) mentions that watcher should be closed asynchronously, which is not the case for Karma code. I'll create a branch with the change and ask you to test it just in case.

`.close()` method returns a Promise now. See fsevents/fsevents#314 (comment). Fixes karma-runner#3511

devoto13 · 2020-05-15T19:29:03Z

Not sure if this will do any good for your particular case, but can you try this fix on your codebase?

Replace "karma": "5.0.5" in your package.json with "karma": "devoto13/karma#chokidar-await" and run npm i. This should install karma from the branch on GitHub.

matthintosh · 2020-05-15T19:50:19Z

I just test with your fix and I still have the same issue.
Assertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 187.
Thank you for your help.

devoto13 · 2020-05-15T20:07:38Z

Okay, then the problem is likely coming from karma-webpack - webpack chain, so not much we can do about it.

matthintosh · 2020-09-28T15:25:51Z

The last version of karma and karm-webpack resolve this issue ! Thank you.

`.close()` method returns a Promise now. See fsevents/fsevents#314 (comment). Fixes karma-runner#3511

The fix turns out to be bumping `webpack` from `4.43` to `4.44` in `packages/web-components`. Prior to this, I'd experience sporadic errors when running `yarn test` like the ones documented in this `karma` issue: [karma-runner/karma#3511](karma-runner/karma#3511). It turns out, that the problem is not with `karma` but rather with `webpack` as documented in [webpack/webpack#10037](webpack/webpack#10037). As per the closing comment in that issue, ensure we use `watchpack` version `^1.7.2` (a transitive dep of `webpack`) is enough to ensure this sporadic error goes away, and to bump `watchpack` we need to bump `webpack` by one minor version.

devoto13 added a commit to devoto13/karma that referenced this issue May 15, 2020

fix(watcher): prevent Node crash when Karma exits

bc6881a

`.close()` method returns a Promise now. See fsevents/fsevents#314 (comment). Fixes karma-runner#3511

devoto13 added the needs: work label May 26, 2020

devoto13 mentioned this issue Jun 12, 2020

fix(client): check in bundled client code into version control #3524

Merged

matthintosh closed this as completed Sep 28, 2020

devoto13 added a commit to devoto13/karma that referenced this issue Jan 18, 2021

fix(watcher): prevent Node crash when Karma exits

d5c02e7

`.close()` method returns a Promise now. See fsevents/fsevents#314 (comment). Fixes karma-runner#3511

kubkon mentioned this issue Jan 18, 2021

fix(libuv): fix sporadic libuv assertion fails microsoft/fluentui#16513

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Assertion failed : (0) at the end of karma execution #3511

Assertion failed : (0) at the end of karma execution #3511

matthintosh commented May 15, 2020 •

edited

Loading

devoto13 commented May 15, 2020

devoto13 commented May 15, 2020 •

edited

Loading

matthintosh commented May 15, 2020

devoto13 commented May 15, 2020

devoto13 commented May 15, 2020

matthintosh commented May 15, 2020

devoto13 commented May 15, 2020

matthintosh commented Sep 28, 2020

Assertion failed : (0) at the end of karma execution #3511

Assertion failed : (0) at the end of karma execution #3511

Comments

matthintosh commented May 15, 2020 • edited Loading

Issue

Error

Software and hardware

Karma config

package.json file

More info

NPM and node version

devoto13 commented May 15, 2020

devoto13 commented May 15, 2020 • edited Loading

matthintosh commented May 15, 2020

devoto13 commented May 15, 2020

devoto13 commented May 15, 2020

matthintosh commented May 15, 2020

devoto13 commented May 15, 2020

matthintosh commented Sep 28, 2020

matthintosh commented May 15, 2020 •

edited

Loading

devoto13 commented May 15, 2020 •

edited

Loading