guysmoilov
commented
9 years ago BTW, I'm running on a Kubuntu 14.10 64 bit VM on top of VirtualBox.
Closed guysmoilov closed 9 years ago
guysmoilov
commented
9 years ago BTW, I'm running on a Kubuntu 14.10 64 bit VM on top of VirtualBox.
ghost
commented
9 years ago Can you first try to update to the latest versions with meteor update. Maybe it's still required to install node for Karma (Client Unit mode).
You can do this easily with nvm.
guysmoilov
commented
9 years ago Thanks for the reply, I did try meteor update, it has no effect. Furthermore, this seems to happen in every project where I try to use meteor-jasmine. As a side effect, I think it causes velocity to report the whole test process as pending indefinitely despite there being no client unit tests and all other tests passing. So maybe this should be an issue on meteor-jasmine or meteor-karma?
If you want, I could try to maybe patch karma to use meteor's node? Not even sure if it's possible...
ghost
commented
9 years ago Can you try if this branch fixes the issue https://github.com/Sanjo/meteor-karma/tree/hotfix/node-path (Branch: hotfix/node-path). If you don't know how to use this branch in you project, I can tell you.
guysmoilov
commented
9 years ago Thanks OK, this is weird. That hotfix didn't help, and from putting debugging messages in files as you see below: https://gist.github.com/guysmoilov/7c814dff5bf8e673f0d5 I can see that all the debug messages in ClientUnitTestFramework.js start method are called and printed successfully, and they show the correct ouput. The log.debug(Karma.start) even shows my own debug line in there! But the debug message in Karma.start never shows! What sorcery is this?
I20150318-19:21:05.520(2)? [sanjo:jasmine]: This is the Karma and Karma.start objects:
I20150318-19:21:05.520(2)? [sanjo:jasmine]: { start: [Function], setConfig: [Function] }
I20150318-19:21:05.521(2)? [sanjo:jasmine]: function (id, options) { // 7
I20150318-19:21:05.522(2)? log.debug("-----------------GUY!!!!!!!!---------") // 8
I20150318-19:21:05.522(2)? log.debug("Inside karma start for client unit tests probably") // 9
I20150318-19:21:05.522(2)? options = options || {} // 10
I20150318-19:21:05.522(2)? log.debug('Karma.start', id) // 11
I20150318-19:21:05.522(2)? // 12
I20150318-19:21:05.528(2)? Karma.setConfig(id, options) // 13
I20150318-19:21:05.529(2)? // 14
I20150318-19:21:05.530(2)? return KarmaInternals.startKarmaServer(id, options) // 15
I20150318-19:21:05.532(2)? }
I20150318-19:21:05.569(2)? [sanjo:jasmine]: No tests for jasmine-server-integration found. Reporting completed.
I20150318-19:21:05.596(2)? [velocity] Mirror requested { framework: 'jasmine-client-integration',
I20150318-19:21:05.596(2)? port: 47391,
I20150318-19:21:05.596(2)? rootUrlPath: '?jasmine=true',
I20150318-19:21:05.596(2)? host: 'http://localhost:47391/',
I20150318-19:21:05.596(2)? rootUrl: 'http://localhost:47391/?jasmine=true' }etc...
ghost
commented
9 years ago What does the .meteor/local/log/jasmin-client-unit.log say? I think the log statements that you have put in are all before the point where the old error happened.
guysmoilov
commented
9 years ago Says the exact same thing as before, and I think I'm an idiot and didn't set the env property for karma logging. Now I get the debug messages.
Now trying to debug why it's not running, I'll update soon.
guysmoilov
commented
9 years ago Finally! Turns out your fix was the right idea, but _.extend doesn't seem to work that way, it doesn't replace values already on the source object... Anyway, I created a pull request for the fix.
ghost
commented
9 years ago Oops. I've confused it with _.defaults. Thanks.
ghost
commented
9 years ago Fixed in sanjo:jasmine 0.12.6.
This is the exact series of commands I executed:
And the HTML view shows client integration\server unit tests passing, but client unit tests are stuck loading forever.
I did notice the following in .meteor/local/log/jasmin-client-unit.log:
That does not look good. I shouldn't have to install node, right?
This is the output of meteor run:
Thanks guys!