Refactor travis ci config and make it run tests under macOS as well

[webknjaz]

I'm submitting this as a follow-up to #149 (comment) (encouraged by @ingydotnet)

Also fixes #200
Closes #212

[webknjaz]

@ingydotnet I think you could ignore a few tests under a specific env and be fine with that.

[webknjaz]

@ingydotnet could you please take a look at this matrix?

[webknjaz]

@ingydotnet ping?

[ingydotnet]

Hi @webknjaz

I'll look at this now. It seems to be failing travis though.

[webknjaz]

@ingydotnet yes, there are a few cases under OSX you mentioned earlier. I can ignore them until they're fixed. Fixing them myself is out of the scope of my intentions in this PR. I just want to help you with infra for testing. I've also added Python 3.7 stable job.

[webknjaz]

Oh.. there's more failures related to rebase on master. I'll fix them. Just do high-level review for now.

[ingydotnet]

@webknjaz If you could patch pyyaml to skip the 5 OSX fails, that would be most appreciated.

Ping me when you get travis passing again.

Feel free to drop by #pyyaml IRC chatroom on irc.freenode.net if you want to chat to the devs in real time.

[webknjaz]

Sure, I'll ignore them and will clean up commits in the branch.

[webknjaz]

@ingydotnet I guess it's ready now

[ingydotnet]

@webknjaz cheers. having a look

[webknjaz]

@ingydotnet I recommend you canceling old PR builds because OS X jobs are really slow and throttled.
By the way, I can change the config in a way that they won't normally run but will run on cron builds (daily) or if triggered manually. This is quite useful if there's lots of incoming code changes simultaneously and you don't want to block processes with waiting for macOS.

[NyanKiyoshi]

You think there is no real risk from breaking the travis build despite Xenial doesn't seem to be officially released by travis?

[ingydotnet]

@webknjaz travis seems to be hanging on the Mac jobs.

[ingydotnet]

@webknjaz just saw your "canceling old PR builds because OS X jobs" comment.

[webknjaz]

You think there is no real risk from breaking the travis build despite Xenial doesn't seem to be officially released by travis?

It must be OK. The only issue is that they attempt to access invalid url of there's no sudo. This way of enabling 3.7 has been suggested by Travis's employee. From my experience with Travis it will be fine.

hanging on the Mac jobs.

@ingydotnet
So do you agree to with running osx only on cron?

[webknjaz]

@ingydotnet I've decided not to wait and went ahead with limiting OS X jobs to manual, cron or tag triggers.

I've also noticed that https://github.com/yaml/pyyaml-build does not build proper manylinux1 wheels (PEP513), so if you want I'll submit a follow-up PR including building manylinux1 wheels for all platforms and completely automatic publish process from travis on tag.

[ingydotnet]

I didn't have time to review everything yet.

[webknjaz]

@ingydotnet we can proceed now.

[webknjaz]

@ingydotnet ping

[webknjaz]

Rebased. I've triggered macOS jobs in my fork as a demo: https://travis-ci.com/webknjaz/pyyaml/builds/104395740.

[webknjaz]

@ingydotnet @perlpunk ^

[cclauss]

Let’s drop Python 3.4 as it’s end of life is in two days.
https://devguide.python.org/#status-of-python-branches

[webknjaz]

@cclauss fair enough... But again, it's not up to me to decide. If maintainers want it, we can remove those. At this stage I just want it to get merged finally...

[webknjaz]

UPD: I've updated Python install method under macOS and now it's 2x faster. This also allows me to drop some entries from the allowed to fail list.

[webknjaz]

✔️ Build is green: https://travis-ci.org/yaml/pyyaml/builds/506258781

[nitzmahone]

handled in #407