Skip to content
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

Get rid of OSX CI builds until they get much faster #707

Merged
merged 1 commit into from
Oct 21, 2016
Merged

Conversation

astorije
Copy link
Member

OSX builds have been nothing but a pain on Travis CI: they fail with no good reason, they stay pending forever, etc.

As far as I can tell, I can't remember one valid build they failed and we legitimately discovered a bug. Dev env on OSX is very close to Linux so it's good enough to have it here.

I'm OK with having AppVeyor running slow, which it often does, but Travis CI should be fast and so far this has been the unfortunate bottleneck.

@astorije astorije added Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. Type: Documentation Lack of documentation, improvement suggestion, or PRs that address these. second review needed labels Oct 20, 2016
@astorije astorije added this to the 2.2.0 milestone Oct 20, 2016
@@ -3,12 +3,6 @@ node_js:
- 6
- 4

matrix:
fast_finish: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep this.

Copy link
Member Author

@astorije astorije Oct 20, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fast_finish is only applied when there is a build with allowed failures set up. We don't need to keep it if we remove OSX builds.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, OSX builds are always longer than Linux builds, so it would alway fast finish...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not only in that case. https://docs.travis-ci.com/user/customizing-the-build/#Fast-Finishing

Again, this only applies if there are jobs in the matrix with allowed failures. We actually have none (the OSX one is not even currently marked as allowed-failures, we would need to have an extra line for that).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright alright alright. But note that if it can be quite a big deal for big projects with long-running builds of multiple jobs (enough to not all run in parallel), it is not even remotely our case on our 2-job-of-1min-something builds...
Clearly splitting hair here but oh well.

OSX builds have been nothing but a pain on Travis CI: they fail with no good reason, they stay pending forever, etc.

As far as I can tell, I can't remember one valid build they failed and we legitimately discovered a bug. Dev env on OSX is very close to Linux so it's good enough to have it here.
@xPaw xPaw merged commit f3f933e into master Oct 21, 2016
@xPaw xPaw deleted the astorije/rm-rf-osx branch October 21, 2016 19:38
matburnham pushed a commit to matburnham/lounge that referenced this pull request Sep 6, 2017
Get rid of OSX CI builds until they get much faster
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issues that report and PRs that solve any defects that cause unexpected behaviors. Type: Documentation Lack of documentation, improvement suggestion, or PRs that address these.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants