Note that tests pass for zmq2, but not zmq3. This behaviour was confirmed locally.
Added Travis CI support.
test.exports now handles version specific options properly.
More on version specific testing.
Some of the flags should have been v3+.
Version checking now delegated to semver.
Merge branch 'master' of git://github.com/JustinTulloss/zeromq.node i…
Rogue console.log removed.
All tests now pass.
Renamed a variable. Didn't make a lot of sense as it was.
Looks good, thanks!
I've merged it, but the build status stays unknown.
@JustinTulloss , could you enable the Travis service hook?
I enabled it, it still says unknown. I think it might be building? I'll look into it again shortly if it doesn't update.
You may need to enable this from the Travis side. There's a box in the service hooks travis CI tab. I used the instructions in there to get it working for me. Make sure that the active box is checked. I made that mistake initially. Probably the problem is the token though.
Even when it is properly set, the build takes a while. The config file I wrote will spawn four workers, so four tests are entered into the queue. When at least one gets the top of the queue and starts the build state will go amber within Travis CI, and if you inspect it you can see the build process itself. It's a little difficult to describe how to navigate that, but you'll know when it's working.
@JustinTulloss so, now after the weekend, it still says build status unknown. Could you have another look? (see @qubyte 's response above)
Is it enabled on this page: https://travis-ci.org/profile ?
@AlexeyKupershtokh Try hitting the Sync now button and seeing if the list updates with the repo. Once it appears, switching to on should complete the configuration. It may or may not require some action (such as a merge into master) to activate a build after this.
@qubyte I don't have any problems :) Just hinting where @JustinTulloss should look for enabling the repo as well.
@AlexeyKupershtokh Ah! My bad. I was on automatic and thought I was talking to @JustinTulloss. :)
@JustinTulloss any update on this?
Appears to be working now.