Error: spawn growlnotify ENOENT

[cssagogo]

Prerequisites

• Checked that your issue isn't already filed by cross referencing issues with the common mistake label
• Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
• 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
• Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with:
  node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend avoiding the use of globally installed Mocha.

Description

I'm unclear if its the same problem discussed here, but having problems running mocha for a newly created project on my mac...

#3067

For the following project...

https://github.com/cssagogo/pikadeck

When I try running the grunt task, I get the following error...

Running "mocha:test" (mocha) task
>> 0 passed! (0.00s)
An error occured. { Error: spawn growlnotify ENOENT
  at _errnoException (util.js:1024:11)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:192:19)
  at onErrorNT (internal/child_process.js:374:16)
  at _combinedTickCallback (internal/process/next_tick.js:138:11)
  at process._tickCallback (internal/process/next_tick.js:180:9)

  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn growlnotify',
  path: 'growlnotify',
  spawnargs: 
   [ '--image',
     '/Users/adamyoungers/projects/pikadeck/node_modules/grunt-mocha/growl/ok.png',
     '-m',
     '0 passed! (0.00s)',
     '0 passed! (0.00s)' ] }

Done.

Process finished with exit code 0

Steps to Reproduce

1. Install project
2. Run grunt test_js task

Expected behavior: Tests to pass

Actual behavior: Get error above

Reproduces how often: Always

Versions

mocha --version: bash: mocha: command not found
node node_modules/.bin/mocha --version: 4.0.1
node --version: v8.8.0
OS: macOS Sierra 10.12.6
grunt-mocha: ^1.0.4

[jlchereau]

On Windows 10 with node 8.9.0, npm-mocha 1.0.4 and mocha 4.0.1

>> 78 passed! (9.97s)
An error occured. { Error: spawn growlnotify ENOENT
    at _errnoException (util.js:1024:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
    at onErrorNT (internal/child_process.js:372:16)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickDomainCallback (internal/process/next_tick.js:218:9)
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn growlnotify',
  path: 'growlnotify',
  spawnargs:
   [ '/i:D:\\WebStorm\\Kidoju\\Kidoju.Mobile\\node_modules\\grunt-mocha\\growl\\ok.png',
     '78 passed! (9.97s)',
     '/t:78 passed! (9.97s)' ] }

[cssagogo]

I updated to node v9.0.0 and npm v5.5.1 and I'm no longer getting this error, but instead a new one. Here is what I have configured in grunt...

        mocha: {
            test2: {
                options: {
                    urls: ['test/index.html'],
                    dest: 'test/index.out',
                    run: true,
                    log: true,
                    reporter: 'Spec',
                    timeout: 10000
                }
            }
        },

And the new error is documented here...

#3090

[cssagogo]

And I spoke to soon. When the test passes I get the original error...

Running "mocha:test2" (mocha) task
Testing: test/index.html


  unitTest.init()
    ✓ Sample Unit test 1

  unitTest.pdf().init()
    ✓ Sample Unit test 2


  2 passing (2ms)

An error occured. { Error: spawn growlnotify ENOENT
>> 2 passed! (0.00s)
  at _errnoException (util.js:1031:13)
  at Process.ChildProcess._handle.onexit (internal/child_process.js:201:19)

Running "clean:css" (clean) task
  at onErrorNT (internal/child_process.js:389:16)
>> 0 paths cleaned.
  at _combinedTickCallback (internal/process/next_tick.js:138:11)
  at process._tickCallback (internal/process/next_tick.js:180:9)


  errno: 'ENOENT',
  code: 'ENOENT',
Running "sass:dev" (sass) task
  syscall: 'spawn growlnotify',
  path: 'growlnotify',
  spawnargs: 
   [ '--image',
     '/Users/adamyoungers/projects/pikadeck/node_modules/grunt-mocha/growl/ok.png',
     '-m',
     '2 passed! (0.00s)',
     '2 passed! (0.00s)' ] }

[mirague]

Seeing this as well, had to disable the --growl flag until this is fixed.

[ScottFreeCode]

Per #3067 (comment), can anyone confirm whether the issue is or is not resolved by installing the respective prerequisite Growl/notify library for their OS?

[toblerpwn]

I can confirm that this works for me.

Ironically, growl was never working; only in Mocha 4 did it expose an error (before that it must have been a silent failure). Running this fixed the problem for me:

sudo gem install terminal-notifier

Although I also needed to add the --exit param to my mocha.opts file. This also only became required in Mocha 4.

(The issues are unrelated except that as of Mocha 4, they both exhibited new issues at the conclusion of tests.)

[bertrandmartel]

As suggested by @mirague, disabling growl in grunt with growlOnSuccess: false fix this :

mocha: {
    all: {
        src: ['tests/testrunner.html']
    },
    options: {
        run: true,
        growlOnSuccess: false
    }
}

[ScottFreeCode]

Does Grunt's growlOnSuccess option for Mocha default to true? If so, we should file a bug report for Grunt to have it default to false -- at least when Growl isn't installed (if need be, it could load the Growl Node library Mocha uses and try using it, try-catching to detect the error and changing the default to false in that case).

[boneskull]

OK, so this isn't a Mocha problem per se; see #3111 instead.

[plroebuck]

It's not Grunt's flag. growlOnSuccess and growlOnFailure are options for the grunt-mocha Grunt task. This package is using Mocha programmatically, but the ENOENT errors are coming from the Grunt task itself (not Mocha).

[kristian-welsh]

For others who encounter this in the future:
None of the above worked for me, but i did manage to disable the feature causing the error by replacing the contents of node_modules/grunt-mocha/node_modules/growl/lib/growl.js with

'use strict';
// do nothing
growl() {

}

[plroebuck]

@kristian-welsh, why not follow the instructions?

[kristian-welsh]

@plroebuck Thank you, I didn't realise that on windows growl needs to be manually installed. I was trying to stop an error thrown by grunt so it would display my test results clearly, if in the future I want notifications I may follow those instructions.