Turn off ng under OSX-CI like we do for linux.
Review Request #3067 - Created Nov. 2, 2015 and submitted
We always should have been doing this, but a recent string of ng related failures brought the old CI configuration issue to light. .travis.osx.yml | 1 + 1 file changed, 1 insertion(+)
This will only be exercised once on master.
is there a reason why Linux CI intentionally does not use nailguns?
it seems like turning this off leaves us prone to undetected nailgun bugs in the integration suite - had this been /on/ in the Linux tests the commit that regressed OSX CI would have never landed as-is. with this on in OSX CI, it's now masking at least one known bug.
should we perhaps be heading in the other direction here in favor of comprehensive integration coverage?