Travis: test against node.js 0.12

[XhmikosR]

/CC @cvrebert @mdo

[cvrebert]

Why not just only test 0.12 and keep things simple?

[XhmikosR]

I don't mind either way. But if we don't test 0.10 we might hit the case where stuff break and we wouldn't know.

Maybe we should keep both for a while and then only use 0.12?

[cvrebert]

I'm wary of the increased chance of transient failures due to the extra builds that would imply.

[XhmikosR]

Why do you think we'd get build failures? I mean, only sauselabs is known to break, the other checks seem to work fine.

Anyway, it's your call. Personally, I use 0.12 myself, but it would be nice to have a way of knowing if things work with 0.10 too in the future. Ideally, we should only have one version to support but it's too early to ditch 0.10...

[kkirsche]

@XhmikosR I've had a number of builds where npm fails to install things correctly on TravisCI causing the tests to fail since they can't find the required modules.

[XhmikosR]

Works fine in our case.

[cvrebert]

I would not call that "fine". False negatives from Travis PR builds are annoying.

[kkirsche]

@XhmikosR I'm referring to builds from Bootstrap's tests.

Two quick examples of pull requests that Travis messed up on: #15744 #15725

[XhmikosR]

I honestly don't see any issue here. The issues arise with the custom npm cache stuff and sauselabs being what it is.

[mdo]

FWIW I'm in favor of whatever is simplest and fastest for our tests.

[XhmikosR]

Well, the fastest would be to only have one node.js version.

If everyone agrees we can drop 0.10 and move to 0.12, then.

Personally, I have switched all my dev VMs to 0.12 and I don't plan going back since things seem to work rather well.

[cvrebert]

Let's just switch to 0.12 then. Although I'd like to wait for uber-archive/npm-shrinkwrap#64 to be resolved first.

[XhmikosR]

OK, I made the change, feel free to merge or ping me if you need something.

[cvrebert]

Cool, the npm-shrinkwrap PR was resolved impressively fast. Regenerated the shrinkwrap. This can be merged as soon as Travis finishes.

[XhmikosR]

@cvrebert: has Travis changed something? We seem to get 2 builds per PR.

[cvrebert]

I think now it's just more apparent since GitHub changed how it displays build statuses.