On Fri, Feb 5, 2016 at 1:16 PM, Chris Barker wrote:
> On Fri, Feb 5, 2016 at 9:55 AM, Nathaniel Smith wrote:
>>
>> > If we set up a numpy-testing conda channel, it could be used to cache
>> > binary builds for all he versions of everything we want to test
>> > against.
>> >
>> > Conda-build-all c
On Fri, Feb 5, 2016 at 3:24 PM, wrote:
>
>
> On Fri, Feb 5, 2016 at 1:14 PM, Pauli Virtanen wrote:
>
>> 05.02.2016, 19:55, Nathaniel Smith kirjoitti:
>> > On Feb 5, 2016 8:28 AM, "Chris Barker - NOAA Federal" <
>> chris.bar...@noaa.gov>
>> > wrote:
>> >>
>> >>> An extra ~2 hours of tests / 6-way
On Fri, Feb 5, 2016 at 9:55 AM, Nathaniel Smith wrote:
> > If we set up a numpy-testing conda channel, it could be used to cache
> > binary builds for all he versions of everything we want to test
> > against.
> >
> > Conda-build-all could make it manageable to maintain that channel.
>
> What wou
05.02.2016, 19:55, Nathaniel Smith kirjoitti:
> On Feb 5, 2016 8:28 AM, "Chris Barker - NOAA Federal"
> wrote:
>>
>>> An extra ~2 hours of tests / 6-way parallelism is not that big a deal
>>> in the grand scheme of things (and I guess it's probably less than
>>> that if we can take advantage of ex
On Feb 5, 2016 8:28 AM, "Chris Barker - NOAA Federal"
wrote:
>
> > An extra ~2 hours of tests / 6-way parallelism is not that big a deal
> > in the grand scheme of things (and I guess it's probably less than
> > that if we can take advantage of existing binary builds)
>
> If we set up a numpy-test
> An extra ~2 hours of tests / 6-way parallelism is not that big a deal
> in the grand scheme of things (and I guess it's probably less than
> that if we can take advantage of existing binary builds)
If we set up a numpy-testing conda channel, it could be used to cache
binary builds for all he ver
