azer / prova

Test runner based on Tape and Browserify

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Browser is hanging when live reload runs

bclinkinbeard opened this issue · comments

run.js is never returning. The read.bundle({ debug: true }).pipe(write); call in lib/browser.js appears to be failing, but I haven't figured out why. Any ideas?

I am running into this on a fresh install of prova.

does it also hang when you run it with a simple file with something simple like example tests ?

Yea, I am running against a single 2+2 test while trying to debug.

On Fri, Apr 18, 2014 at 5:19 PM, Azer Koçulu notifications@github.com
wrote:

does it also hang when you run it with a simple file with example tests ?

Reply to this email directly or view it on GitHub:
#9 (comment)

that's weird, I'm at work right now, will look at it as soon as I have free time

Thanks, I appreciate it. For convenience here is the simple test file I'm running.

var test = require('prova')

test('addition', function (t) {
    t.equal(2 + 2, 4)
    t.end()
})

OK I kept digging and write is not getting called on the subsequent runs. No idea why, but changing that line to the following fixes the issue.

read.bundle({ debug: true }, function (err, src) {
      res.end(src)
  })

It also happens when browserify fails to build, so, I've just published a new version (1.1.1) that outputs an error message when browserify fails. Could you install it and see how it fails?

(p.s it fails on the console, the browser doesn't output anything)

Cool, I'm afk for a while but will try later tonight. Fwiw, write wasn't being called even when there was no error (according to the callback).

On Fri, Apr 18, 2014 at 6:23 PM, Azer Koçulu notifications@github.com
wrote:

(p.s it fails on the console, the browser doesn't output anything)

Reply to this email directly or view it on GitHub:
#9 (comment)

Same issue with 1.1.1

No error, and write is not called on rebundle. Are you able to reproduce this behavior?

nope. I tried with node 0.10.26 and 25, both worked

Crap, something is going on with my system then but I have no idea what. This just started happening today and I can't imagine what would cause this kind of issue. It happens in all browsers and persists across restarts.

Do you use nvm ? You can switch between minor versions like 26 25 24

No, but I was running 21 until a few minutes ago. Upgraded to 26 and still no dice.

On April 18, 2014 at 8:14:44 PM, Azer Koçulu (notifications@github.com) wrote:

Do you use nvm ? You can switch between minor versions like 26 25 24


Reply to this email directly or view it on GitHub.