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

Bug in triggered build travis matrix #147

Closed
springmeyer opened this issue Apr 6, 2016 · 2 comments
Closed

Bug in triggered build travis matrix #147

springmeyer opened this issue Apr 6, 2016 · 2 comments

Comments

@springmeyer
Copy link
Contributor

It looks like triggered builds are not creating the matrix correctly because we are getting 4 jobs rather than 2. For example for gdal 2.0.2 this matrix is used with 2 entries (one for each operating system) but travis gets 4: https://travis-ci.org/mapbox/mason/builds/121252415

/cc @jfirebaugh in case he has ideas.

@jfirebaugh
Copy link
Contributor

I believe this is a Travis bug: travis-ci/travis-ci#4681

@springmeyer
Copy link
Contributor Author

Thanks @jfirebaugh - I was aware of that behavior, but confused because we are not using any global setting like compiler. But then I realized that the main travis.yml was likely being inherited and we have a global os setting. Removing that fixed the problem: 5026db6.

I've been thinking we should ditch testing on osx anyway to avoid the delays. If we want to re-introduce OS X testing for the main repo run we could likely dodge this bug by nesting the os inside matrix: include.

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

No branches or pull requests

2 participants