Run Travis tests on OS X

[lukechilds]

As discussed in #1266

These are probs gonna fail for the first few builds, just need the PR open for Travis results. I'll mention you when I've got it working.

[ljharb]

@lukechilds do you still plan to get this in?

[lukechilds]

Sorry, I'm currently traveling without reliable internet access and will be for the next few weeks. I'm happy to continue on this when I've got a base setup but from what I remember I was struggling quite a bit to get the install from source tests to build. If you're trying to clear out old prs/issues then feel free to close this and I'll reopen when I continue working on it.

[ljharb]

@lukechilds np, i'm happy to leave it open as long as you like, just pinging for confirmation it's still planned :-)

[PeterDaveHello]

I'm looking into that issue, too. I think it's no ways to do the tests easily as we have too many matrixes, as Travis CI has no plan on supporting multi-dimensional matrixes yet(travis-ci/travis-ci#1519), we'll need to use matrix.include to configure every matrixes as per https://docs.travis-ci.com/user/multi-os/#Example-Multi-OS-Build-Matrix, so each matrix will looks like:

- os: linux
  dist: trusty
  sudo: required
  addons:
    apt:
      packages:
        - cabal-install
        - zsh
      #  - ksh
      #  - gcc-4.8
      #  - g++-4.8
  install:
    - if [ -n "${SHELLCHECK-}" ]; then cabal update && cabal install ShellCheck && shellcheck --version ; fi
    - if [ -z "${SHELLCHECK-}" ]; then nvm install node && npm install && npm prune && npm ls urchin doctoc; fi
  env:
    - SHELL=bash TEST_SUITE=install_script

outside each matrix, the upper level will be:

matrix:
  include:

by current, we have 37 matrixes ... so the yaml file will be SUPER long, complex and hard to maintain ... (think about 37 x 17 lines), the most easiest way may be to separate out osx or linux tests into another CI platform, @ljharb do you have any idea yet?

[ljharb]

I've used OS X tests on other projects since this was filed, and travis-ci does not yet have sufficient OS X build capacity for this to be hugely useful with more than a couple jobs.

[PeterDaveHello]

Tried something else like Circle CI? Or even Jenkins, Mac OS server, but the later two options need self hosting.

[ljharb]

Anything that requires self-hosting isn't an option. I've explored the node build team giving me access to their private hardware though, and that would likely be the best direction.

[PeterDaveHello]

I'll call the private hardware self-hosting ha :)

[PeterDaveHello]

So what can we do for this part since only you have the access?

[ljharb]

Probably nothing for now.

[ljharb]

@lukechilds i know it's been awhile :-) but if you wanted to try adding OS X tests to github actions, that would be amazing.