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

Configure travis to additionally test "full" builds #1033

Closed
durack1 opened this Issue Feb 12, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@durack1
Member

durack1 commented Feb 12, 2015

It seems that currently travis is only testing "default" builds, which exclude a number of packages that are built during a "full" build (Cython, Matplotlib, Spyder, iPython and many others).

It would be good to configure travis to additionally test "full" builds so that any issue cropping up with these additional libraries will be discovered when the PR is issued - may as well get travis tests working across the full build system.

The issue is discussed within #1025, #1023, #921, #941, #856..

@doutriaux1 @aashish24 can you set this as a 2.2+ milestone?

@durack1

This comment has been minimized.

Member

durack1 commented Feb 19, 2015

@doutriaux1 another 2.3 candidate..

@doutriaux1 doutriaux1 added this to the 2.3 milestone Feb 19, 2015

@durack1

This comment has been minimized.

Member

durack1 commented Feb 25, 2015

@doutriaux1 @aashish24 it would seem that travis-ci has a build timeout of 120 mins vs 50 for travis.

It also seems that using the build matrix differing build options should be configurable..

It would be very helpful to convert builds to test ALL as I've just managed to introduce a couple of problems with recent PRs that should have been identified if the added packages were in fact built

@durack1

This comment has been minimized.

Member

durack1 commented Jun 1, 2015

@doutriaux1 @aashish24 has this issue been rendered obsolete with the new build_bot testing? If so please close.

@aashish24

This comment has been minimized.

Contributor

aashish24 commented Jun 2, 2015

Yes, it is obsolete.

@aashish24 aashish24 closed this Jun 2, 2015

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