-
Notifications
You must be signed in to change notification settings - Fork 364
Fix mocha tests #130
Comments
I think this is an issue with practicalmeteor:mocha. I don't think it actually matters, but it would be good to clean it up. Perhaps you could open a issue over there? |
@tmeasday Was due to out-of-date mocha and release. There are a few more out-of-date packages, maybe we can try a general |
looks like i broke CI, sorry. looking into it |
@lorensr let me take a look |
I think the no route for path error is normal, because we are running w/o the routes file. It shouldn't be a problem however. |
Is there a way to tell what context you're running in, so that FR could not throw the error when it's in non- |
Yeah, definitely. FR should probably not throw when |
So it seems just like a problem with |
cc @aldeed ---I'm not sure if we are doing something wrong but this seems like a bug |
That makes sense to me. It's possible that'll break their tests; it could be acceptable to just have the first guard. |
I'll try and repro this against dispatch:mocha-phantomjs |
Is it latest mocha-phantomjs? |
Yeah it happens with 0.1.0 |
(I'll push that todos/master) |
So its seems to be a problem with the interaction between You can trivially repo it by just including them both in a project: https://github.com/tmeasday/mocha-phantom-problem |
@aldeed can we figure out a way to do practicalmeteor/meteor-mocha#23 (comment) ? |
@tmeasday You could submit a PR for practicalmeteor/mocha. I haven't had time to look into it and it will realistically be another week before I will. |
@lorensr I probably won't have time to look at this, so unless you are keen to do so maybe we should revert the last few commits for now |
@tmeasday Okay. I just made the one, so like On Wed, May 4, 2016 at 8:08 PM, Tom Coleman notifications@github.com
|
Oh, you made one too. Okay, I did |
The |
The text was updated successfully, but these errors were encountered: