Ok no worries — I just want to make sure that I'm not way off on what the causes of the failures are... Sometimes Travis errors are misleading. Who's running the actual server and do we have any logs about uptime?

On Tue, Dec 9, 2014 at 1:41 PM, Steven Silvester <steven.silvester@gmail.com> wrote:
Juan, 

I'm not sure what is causing the recent failures.  We have been using the new travis-wheels site for over a month:  https://github.com/scikit-image/scikit-image/commit/b6f775a7cf8c775d89e8fe203cd2e0f874be5965.  Perhaps the rackspace server is having some trouble.


- Steve

On Sunday, December 7, 2014 5:00:58 PM UTC-6, Juan Nunez-Iglesias wrote:
A bunch of Travis errors are being caused (apparently) by travis-wheels.scikit-image.org not responding. I haven't been following the discussion closely, but my question is, do we need to get rid of it for the Travis build so that we can have a stable build system at the sprint? Or do we perhaps want to add a condition to use regular pip builds if travis-wheels is unavailable?


--
You received this message because you are subscribed to the Google Groups "scikit-image" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.