crashes on save

[bibodha]

Karma v0.12.0
Browswer: Chrome 33.0.1750 (Windows 7)
Windows 7 running on VMWare on Mac OSX 10.9

Error Message:

ERROR [karma]: { [Error: ENOENT, stat 'c:\Projects\demo\test\appSpec.js']
  errno: 34,
  code: 'ENOENT',
path: 'c:\\Projects\\demo\\test\\appSpec.js' }
Error: ENOENT, stat 'c:\Projects\demo\test\appSpec.js'
INFO [watcher]: Changed file "c:/Projects/demo/test/appSpec.js".

This also happens when running PhantomJS instead of Chrome and happens very frequently.

[MaikuMori]

I also have this happening on Linux (Archlinux) using Karma 0.12.1:

INFO [watcher]: Changed file "/home/maiku/Projects/xxx/xxx/test/utils/xxx.js".
ERROR [karma]: { [Error: ENOENT, stat '/home/maiku/Projects/xxx/xxx/test/utils/xxx.js___jb_bak___']
  errno: 34,
  code: 'ENOENT',
  path: '/home/maiku/Projects/xxx/xxx/test/utils/xxx.js___jb_bak___' }
Error: ENOENT, stat '/home/maiku/Projects/xxx/xxx/test/utils/xxx.js___jb_bak___'

.js___jb_bak___ seems a bit strange, could be a file created by my IDE (PyCharm) when I save.

EDIT:
Just for completeness my include patterns are these:

{pattern: 'src/**/*.js', included: false},
{pattern: 'test/**/*Spec.js', included: false},

So it should not even include those temp files even if they're created on save and then deleted.

[bibodha]

a workaround for this is running karma with auto-watch false and doing karma run. Kinda defeats the purpose but if you don't want it to crash on every save.

[dignifiedquire]

This sounds like an issue with the respective editors in use. What are you using @bibodha?

[MaikuMori]

While it might be editor that is producing the bug, it's not the editors issue that karma fails. Karma in first place shouldn't match .js___jb_bak___ even if it's there.

My wild guess it's a race condition - karma gets notified that there is a change, it follows up with stat on the file, but the file is already deleted.

[MaikuMori]

Looks like the problem is here: https://github.com/karma-runner/karma/blob/master/lib/file_list.js#L305

The file is gone by the time stat is being called. I guess having SSD + Linux with it's filesystem caching magic improves the chance to get this error.

[bibodha]

@dignifiedquire
My setup is as follows:

As mentioned previously: VMWare Fusion 6.0.2 on Mac OSX v10.9.2
Text Editor: GVim and Visual Studio 2013
Running on GitBash on Console2

Plugins: jasmine, require, coverage, phantomjs-launcher, chrome-launcher

[vojtajina]

@MaikuMori can you put **/*.js___jb_bak___ into exclude config? That should work around the issue for now.

Can you guys also try setting usePolling: false?

Yep, this is a bug,

karma/lib/file_list.js

Line 305 in cc6386f

return fs.stat(path, function(err, stat) {

should ignore if there is an error.

Actually, when fixing this. We should not do the stat, if the stat is already provided by chokidar (when usePolling: true, chokidar already stats the file and gives us the stat, we should use it). See #469

[DanTup]

Possibly this is the same issue as #959? File gets renamed before Chokidar stats it; then the stat fails. PR #1020 should fix the crash; though whether it leaves any issues with changes not being detected, I'm not yet sure (haven't seen it; but if there are unhandled races between the editor and Chokidar, it might be a possibility)

[dignifiedquire]

Is this still an issue?

[devoto13]

As we haven't heard any more reports of this problem in 4 years, I think it is pretty safe to assume that it was resolved. Happy to re-open if anybody still experiences the problem and can provide a reproduction.