vows/test/commands/*.js fails, but individual tests pass. about jitsu HOT 4 CLOSED

1. The TypeError is coming from inside of node.js core, which is why it is being obscured. It is being thrown inside of the equal I believe.
2. This concept of "run individual file" and it passes and "run all files" and it fails is something I've seen before, I can poke around and abstract it away I think. I did it in haibu and our core pretty well.

@dominictarr Thanks for this, good catch. If you can take care of converting the other two test files I mentioned in the pull request I should be able to take a stab at this tomorrow and we can merge it in and move on.

Cheers.

from jitsu.

yup, working on it.

Since this is my last week in US I'm catching up on some touristy things,
(today is computer histroy muesum!) but if not today, then definately
tomorrow.

On Thu, Jun 23, 2011 at 12:33 AM, indexzero <
[email protected]>wrote:

1. The TypeError is coming from inside of node.js core, which is why it is
   being obscured. It is being thrown inside of the equal I believe.
2. This concept of "run individual file" and it passes and "run all files"
   and it fails is something I've seen before, I can poke around and abstract
   it away I think. I did it in haibu and our core pretty well.

@dominictarr Thanks for this, good catch. If you can take care of
converting the other two test files I mentioned in the pull request I should
be able to take a stab at this tomorrow and we can merge it in and move on.

Cheers.

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

from jitsu.

oh damn, some of the product code has changed and now the tests need to be
different (such as this commit to
nodejitsu/node-prompt@7de4316
prompt)

On Thu, Jun 23, 2011 at 10:15 AM, Dominic Tarr [email protected]:

yup, working on it.

Since this is my last week in US I'm catching up on some touristy things,
(today is computer histroy muesum!) but if not today, then definately
tomorrow.

On Thu, Jun 23, 2011 at 12:33 AM, indexzero <
[email protected]>wrote:

1. The TypeError is coming from inside of node.js core, which is why it is
   being obscured. It is being thrown inside of the equal I believe.
2. This concept of "run individual file" and it passes and "run all files"
   and it fails is something I've seen before, I can poke around and abstract
   it away I think. I did it in haibu and our core pretty well.

@dominictarr Thanks for this, good catch. If you can take care of
converting the other two test files I mentioned in the pull request I should
be able to take a stab at this tomorrow and we can merge it in and move on.

Cheers.

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

from jitsu.

This is fixed in head

from jitsu.