Skip to content

macOS continuous integration #1072

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pepyakin opened this issue Oct 10, 2017 · 2 comments · Fixed by #1810
Closed

macOS continuous integration #1072

pepyakin opened this issue Oct 10, 2017 · 2 comments · Fixed by #1810

Comments

@pepyakin
Copy link
Contributor

pepyakin commented Oct 10, 2017

The last two issues (1, 2) with macOS build made it clear that we need macOS CI.

@fitzgen noted that once upon a time there was macOS builds on Travis CI, but since they took very long time they were disabled.

Maybe it is worth to run the "full suite" asynchroniously after the merge?

@pepyakin
Copy link
Contributor Author

Also, these failures made me to explore the ways running the tests on linux on my macOS machine.

So I came up with this Dockerfile. I'm wondering is it worth to check it in?

@fitzgen
Copy link
Member

fitzgen commented Oct 11, 2017

It wasn't that the tests themselves took a long time, it was that Travis CI doesn't have very many macos builders, and so the wait time was something like 2-4 hours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants