Re: [Numpy-discussion] Appveyor Testing Changes

[Ralf Gommers]

On Tue, Jan 26, 2016 at 2:13 AM, G Young  wrote:

> Ah, yes, that is true.  That point had completely escaped my mind.  In
> light of this, it seems that it's not worth the while then to completely
> switch over to pip + virtualenv.  It's might be better actually to rewrite
> the current Appveyor tests to use environments so that the test suite can
> be expanded, though I'm not sure how prudent that is given how slow
> Appveyor tests run.
>

At the moment Appveyor is already a bit of a bottleneck - it regularly
hasn't started yet when TravisCI is already done. This can be solved via a
paid account, we should seriously consider that when we have a bit more
experience with it (Appveyor tests have been running for less than a month
I think). But it does mean we should go for a sparse test matrix, and use a
more complete one (all Python versions for example) on TravisCI. In the
near future we'll have to add MingwPy test runs to Appveyor. Beyond that
I'm not sure what needs to be added?

Ralf



>
> Greg
>
> On Tue, Jan 26, 2016 at 12:13 AM, Bryan Van de Ven 
> wrote:
>
>>
>> > On Jan 25, 2016, at 5:21 PM, G Young  wrote:
>> >
>> > With regards to testing numpy, both Conda and Pip + Virtualenv work
>> quite well.  I have used both to install master and run unit tests, and
>> both pass with flying colors.  This chart here illustrates my point nicely
>> as well.
>> >
>> > However, I can't seem to find / access Conda installations for slightly
>> older versions of Python (e.g. Python 3.4).  Perhaps this is not much of an
>> issue now with the next release (1.12) being written only for Python 2.7
>> and Python 3.4 - 5.  However, if we were to wind the clock slightly back to
>> when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being
>> able to test on a variety of Python distributions given the nature of Conda
>> releases.  Maybe that situation is no longer the case now, but in the long
>> term, it could easily happen again.
>>
>> Why do you need the installers? The whole point of conda is to be able to
>> create environments with whatever configuration you need. Just pick the
>> newest installer and use "conda create" from there:
>>
>> bryan@0199-bryanv (git:streaming) ~/work/bokeh/bokeh $ conda create -n
>> py26 python=2.6
>> Fetching package metadata: ..
>> Solving package specifications: ..
>> Package plan for installation in environment
>> /Users/bryan/anaconda/envs/py26:
>>
>> The following packages will be downloaded:
>>
>> package|build
>> ---|-
>> setuptools-18.0.1  |   py26_0 343 KB
>> pip-7.1.0  |   py26_0 1.4 MB
>> 
>>Total: 1.7 MB
>>
>> The following NEW packages will be INSTALLED:
>>
>> openssl:1.0.1k-1
>> pip:7.1.0-py26_0
>> python: 2.6.9-1
>> readline:   6.2-2
>> setuptools: 18.0.1-py26_0
>> sqlite: 3.9.2-0
>> tk: 8.5.18-0
>> zlib:   1.2.8-0
>>
>> Proceed ([y]/n)?
>>
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[G Young]

Perhaps a pip + virtualenv build as well since that's one way that is
mentioned in the online docs for installing source code.  I can't think of
anything else beyond that and what you suggested for the time being.

Greg

On Tue, Jan 26, 2016 at 6:59 PM, Ralf Gommers 
wrote:

>
>
> On Tue, Jan 26, 2016 at 2:13 AM, G Young  wrote:
>
>> Ah, yes, that is true.  That point had completely escaped my mind.  In
>> light of this, it seems that it's not worth the while then to completely
>> switch over to pip + virtualenv.  It's might be better actually to rewrite
>> the current Appveyor tests to use environments so that the test suite can
>> be expanded, though I'm not sure how prudent that is given how slow
>> Appveyor tests run.
>>
>
> At the moment Appveyor is already a bit of a bottleneck - it regularly
> hasn't started yet when TravisCI is already done. This can be solved via a
> paid account, we should seriously consider that when we have a bit more
> experience with it (Appveyor tests have been running for less than a month
> I think). But it does mean we should go for a sparse test matrix, and use a
> more complete one (all Python versions for example) on TravisCI. In the
> near future we'll have to add MingwPy test runs to Appveyor. Beyond that
> I'm not sure what needs to be added?
>
> Ralf
>
>
>
>>
>> Greg
>>
>> On Tue, Jan 26, 2016 at 12:13 AM, Bryan Van de Ven 
>> wrote:
>>
>>>
>>> > On Jan 25, 2016, at 5:21 PM, G Young  wrote:
>>> >
>>> > With regards to testing numpy, both Conda and Pip + Virtualenv work
>>> quite well.  I have used both to install master and run unit tests, and
>>> both pass with flying colors.  This chart here illustrates my point nicely
>>> as well.
>>> >
>>> > However, I can't seem to find / access Conda installations for
>>> slightly older versions of Python (e.g. Python 3.4).  Perhaps this is not
>>> much of an issue now with the next release (1.12) being written only for
>>> Python 2.7 and Python 3.4 - 5.  However, if we were to wind the clock
>>> slightly back to when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls
>>> short in being able to test on a variety of Python distributions given the
>>> nature of Conda releases.  Maybe that situation is no longer the case now,
>>> but in the long term, it could easily happen again.
>>>
>>> Why do you need the installers? The whole point of conda is to be able
>>> to create environments with whatever configuration you need. Just pick the
>>> newest installer and use "conda create" from there:
>>>
>>> bryan@0199-bryanv (git:streaming) ~/work/bokeh/bokeh $ conda create -n
>>> py26 python=2.6
>>> Fetching package metadata: ..
>>> Solving package specifications: ..
>>> Package plan for installation in environment
>>> /Users/bryan/anaconda/envs/py26:
>>>
>>> The following packages will be downloaded:
>>>
>>> package|build
>>> ---|-
>>> setuptools-18.0.1  |   py26_0 343 KB
>>> pip-7.1.0  |   py26_0 1.4 MB
>>> 
>>>Total: 1.7 MB
>>>
>>> The following NEW packages will be INSTALLED:
>>>
>>> openssl:1.0.1k-1
>>> pip:7.1.0-py26_0
>>> python: 2.6.9-1
>>> readline:   6.2-2
>>> setuptools: 18.0.1-py26_0
>>> sqlite: 3.9.2-0
>>> tk: 8.5.18-0
>>> zlib:   1.2.8-0
>>>
>>> Proceed ([y]/n)?
>>>
>>> ___
>>> NumPy-Discussion mailing list
>>> NumPy-Discussion@scipy.org
>>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>>
>>
>>
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[Nathaniel Smith]

On Mon, Jan 25, 2016 at 2:37 PM, G Young  wrote:
> Hello all,
>
> I currently have a branch on my fork (not PR) where I am experimenting with
> running Appveyor CI via Virtualenv instead of Conda.  I have build running
> here.  What do people think of using Virtualenv (as we do on Travis) instead
> of Conda for testing?

Can you summarize the advantages and disadvantages that you're aware of?

-n

-- 
Nathaniel J. Smith -- https://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[G Young]

Hello all,

I currently have a branch on my fork (not PR) where I am experimenting with
running Appveyor CI via Virtualenv instead of Conda.  I have build running
here .
What do people think of using Virtualenv (as we do on Travis) instead of
Conda for testing?

Thanks,

Greg
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[G Young]

With regards to testing numpy, both Conda and Pip + Virtualenv work quite
well.  I have used both to install master and run unit tests, and both pass
with flying colors.  This chart here

illustrates
my point nicely as well.

However, I can't seem to find / access Conda installations for slightly
older versions of Python (e.g. Python 3.4).  Perhaps this is not much of an
issue now with the next release (1.12) being written only for Python 2.7
and Python 3.4 - 5.  However, if we were to wind the clock slightly back to
when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being
able to test on a variety of Python distributions given the nature of Conda
releases.  Maybe that situation is no longer the case now, but in the long
term, it could easily happen again.

Greg


On Mon, Jan 25, 2016 at 10:50 PM, Nathaniel Smith  wrote:

> On Mon, Jan 25, 2016 at 2:37 PM, G Young  wrote:
> > Hello all,
> >
> > I currently have a branch on my fork (not PR) where I am experimenting
> with
> > running Appveyor CI via Virtualenv instead of Conda.  I have build
> running
> > here.  What do people think of using Virtualenv (as we do on Travis)
> instead
> > of Conda for testing?
>
> Can you summarize the advantages and disadvantages that you're aware of?
>
> -n
>
> --
> Nathaniel J. Smith -- https://vorpus.org
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[Michael Sarahan]

Conda can generally install older versions of python in environments:

conda create -n myenv python=3.4

You really don't need any particular initial version of python/conda in
order to do this.  You do, however, need to activate the new environment to
use it:

activate myenv

(For windows, you do not need "source")

Hth,
Michael

On Mon, Jan 25, 2016, 17:21 G Young  wrote:

> With regards to testing numpy, both Conda and Pip + Virtualenv work quite
> well.  I have used both to install master and run unit tests, and both pass
> with flying colors.  This chart here
> 
>  illustrates
> my point nicely as well.
>
> However, I can't seem to find / access Conda installations for slightly
> older versions of Python (e.g. Python 3.4).  Perhaps this is not much of an
> issue now with the next release (1.12) being written only for Python 2.7
> and Python 3.4 - 5.  However, if we were to wind the clock slightly back to
> when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being
> able to test on a variety of Python distributions given the nature of Conda
> releases.  Maybe that situation is no longer the case now, but in the long
> term, it could easily happen again.
>
> Greg
>
>
> On Mon, Jan 25, 2016 at 10:50 PM, Nathaniel Smith  wrote:
>
>> On Mon, Jan 25, 2016 at 2:37 PM, G Young  wrote:
>> > Hello all,
>> >
>> > I currently have a branch on my fork (not PR) where I am experimenting
>> with
>> > running Appveyor CI via Virtualenv instead of Conda.  I have build
>> running
>> > here.  What do people think of using Virtualenv (as we do on Travis)
>> instead
>> > of Conda for testing?
>>
>> Can you summarize the advantages and disadvantages that you're aware of?
>>
>> -n
>>
>> --
>> Nathaniel J. Smith -- https://vorpus.org
>> ___
>> NumPy-Discussion mailing list
>> NumPy-Discussion@scipy.org
>> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[Bryan Van de Ven]

> On Jan 25, 2016, at 5:21 PM, G Young  wrote:
> 
> With regards to testing numpy, both Conda and Pip + Virtualenv work quite 
> well.  I have used both to install master and run unit tests, and both pass 
> with flying colors.  This chart here illustrates my point nicely as well.  
> 
> However, I can't seem to find / access Conda installations for slightly older 
> versions of Python (e.g. Python 3.4).  Perhaps this is not much of an issue 
> now with the next release (1.12) being written only for Python 2.7 and Python 
> 3.4 - 5.  However, if we were to wind the clock slightly back to when we were 
> testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being able to test on a 
> variety of Python distributions given the nature of Conda releases.  Maybe 
> that situation is no longer the case now, but in the long term, it could 
> easily happen again.

Why do you need the installers? The whole point of conda is to be able to 
create environments with whatever configuration you need. Just pick the newest 
installer and use "conda create" from there:

bryan@0199-bryanv (git:streaming) ~/work/bokeh/bokeh $ conda create -n py26 
python=2.6
Fetching package metadata: ..
Solving package specifications: ..
Package plan for installation in environment /Users/bryan/anaconda/envs/py26:

The following packages will be downloaded:

package|build
---|-
setuptools-18.0.1  |   py26_0 343 KB
pip-7.1.0  |   py26_0 1.4 MB

   Total: 1.7 MB

The following NEW packages will be INSTALLED:

openssl:1.0.1k-1 
pip:7.1.0-py26_0 
python: 2.6.9-1  
readline:   6.2-2
setuptools: 18.0.1-py26_0
sqlite: 3.9.2-0  
tk: 8.5.18-0 
zlib:   1.2.8-0  

Proceed ([y]/n)? 

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Appveyor Testing Changes

[G Young]

Ah, yes, that is true.  That point had completely escaped my mind.  In
light of this, it seems that it's not worth the while then to completely
switch over to pip + virtualenv.  It's might be better actually to rewrite
the current Appveyor tests to use environments so that the test suite can
be expanded, though I'm not sure how prudent that is given how slow
Appveyor tests run.

Greg

On Tue, Jan 26, 2016 at 12:13 AM, Bryan Van de Ven 
wrote:

>
> > On Jan 25, 2016, at 5:21 PM, G Young  wrote:
> >
> > With regards to testing numpy, both Conda and Pip + Virtualenv work
> quite well.  I have used both to install master and run unit tests, and
> both pass with flying colors.  This chart here illustrates my point nicely
> as well.
> >
> > However, I can't seem to find / access Conda installations for slightly
> older versions of Python (e.g. Python 3.4).  Perhaps this is not much of an
> issue now with the next release (1.12) being written only for Python 2.7
> and Python 3.4 - 5.  However, if we were to wind the clock slightly back to
> when we were testing 2.6 - 7, 3.2 - 5, I feel Conda falls short in being
> able to test on a variety of Python distributions given the nature of Conda
> releases.  Maybe that situation is no longer the case now, but in the long
> term, it could easily happen again.
>
> Why do you need the installers? The whole point of conda is to be able to
> create environments with whatever configuration you need. Just pick the
> newest installer and use "conda create" from there:
>
> bryan@0199-bryanv (git:streaming) ~/work/bokeh/bokeh $ conda create -n
> py26 python=2.6
> Fetching package metadata: ..
> Solving package specifications: ..
> Package plan for installation in environment
> /Users/bryan/anaconda/envs/py26:
>
> The following packages will be downloaded:
>
> package|build
> ---|-
> setuptools-18.0.1  |   py26_0 343 KB
> pip-7.1.0  |   py26_0 1.4 MB
> 
>Total: 1.7 MB
>
> The following NEW packages will be INSTALLED:
>
> openssl:1.0.1k-1
> pip:7.1.0-py26_0
> python: 2.6.9-1
> readline:   6.2-2
> setuptools: 18.0.1-py26_0
> sqlite: 3.9.2-0
> tk: 8.5.18-0
> zlib:   1.2.8-0
>
> Proceed ([y]/n)?
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ian Henriksen]

On Tue, Dec 22, 2015 at 12:14 AM Ralf Gommers 
wrote:

> That would be quite useful I think. 32/64-bit issues are mostly orthogonal
> to py2/py3 ones, so may only a 32-bit Python 3.5 build to keep things fast?
>

Done in https://github.com/numpy/numpy/pull/6874.
Hope this helps,
-Ian
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ralf Gommers]

On Tue, Dec 22, 2015 at 9:25 PM, Ian Henriksen <
insertinterestingnameh...@gmail.com> wrote:

> On Tue, Dec 22, 2015 at 12:14 AM Ralf Gommers 
> wrote:
>
>> That would be quite useful I think. 32/64-bit issues are mostly
>> orthogonal to py2/py3 ones, so may only a 32-bit Python 3.5 build to keep
>> things fast?
>>
>
> Done in https://github.com/numpy/numpy/pull/6874.
> Hope this helps,
>

Great, thanks again Ian!

Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ian Henriksen]

>
> Also, am I correct that these are win64 builds only? Anyone know if it
> would be easy to add win32?
>

It'd be really easy to add 32 bit builds. The main reason I didn't was
because appveyor only
gives one concurrent build job for free, and I didn't want to slow things
down too much. I can get
a PR up for 32 bit builds too if you'd like.

Some background: I based the initial setup off of the dynd-python appveyor
setup
(https://github.com/libdynd/dynd-python/blob/master/appveyor.yml) where we
do one 32 and one
64 bit build. For fancier selection of Python installation, there's a demo
at
https://github.com/ogrisel/python-appveyor-demo that looks promising as
well. I avoided that
initially because it's a lot more complex than just a single appveyor.yml
file.

Best,
-Ian
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ian Henriksen]

>
> The Python 3 build runs much faster than the Python 2. You can close and
>> reopen my testing PR to check what happens if you enable the numpy project.
>
>
I'm not sure why this is the case. MSVC 2015 is generally better about a
lot of things, but it's
surprising that the speed difference is so large.
Best,
-Ian
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ralf Gommers]

On Mon, Dec 21, 2015 at 7:42 PM, Ian Henriksen <
insertinterestingnameh...@gmail.com> wrote:

> Also, am I correct that these are win64 builds only? Anyone know if it
>> would be easy to add win32?
>>
>
> It'd be really easy to add 32 bit builds. The main reason I didn't was
> because appveyor only
> gives one concurrent build job for free, and I didn't want to slow things
> down too much. I can get
> a PR up for 32 bit builds too if you'd like.
>

That would be quite useful I think. 32/64-bit issues are mostly orthogonal
to py2/py3 ones, so may only a 32-bit Python 3.5 build to keep things fast?

Ralf 
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 4:27 PM, Charles R Harris  wrote:

>
>
> On Sun, Dec 20, 2015 at 4:22 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> 
>>
>> > The work is in convincing the one person (that I know about) who has
>> access to the appropriate permissions to pay attention to my email... I've
>> made several attempts at getting this set up with no effect so far :-/ But
>> yeah, it does need to be done in any case so I'll try again.
>>
>> I tried simple and dumb, just enabled the numpy repository from my
>> personal appveyor account. A test PR shows both travis and appveyor
>> running. Now, that may be just for my PRs, so can someone else try a test
>> PR and see if the tests run?
>>
>>
> PS, you need to base on current master.
>

And added an AppVeyor team to the numpy organization as suggested here
. Shrug, I don't know
if it makes any difference, but you can add yourself.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 8:11 PM, Nathaniel Smith  wrote:

> On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris
>  wrote:
> >
> >
> > On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith  wrote:
> >>
> [...]
> >> Also, am I correct that these are win64 builds only? Anyone know if it
> >> would be easy to add win32?
> >
> >
> > Don't know. I also noticed a bunch of permission errors with temp files.
> > There are some failing tests that are filtered out with our preliminary
> > appveyor script.
>
> Yeah, looking at the logs for
>
> https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/9lkl8940dvhrml2v
>
> https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/awgp7fnne15jwb21
> there appears to be some configuration weirdness that makes temp files
> unwriteable so all the tests that use those fail, plus some mysterious
> issue with distutils.msvc9compiler, plus what's probably a genuine
> error in mtrand.pyx where it is expecting 'long' to be 64 bits (which
> it is on every 64-bit platform we support *except* for win64), plus
> what's probably a genuine problem with test_diophantine_fuzz (py3 only
> -- maybe some PyInt/PyLong transition issue?).
>
> > Nathaniel, if you have an appveyor account that lets you have access to
> the
> > numpy repo, could you try enabling it and see what happens? I note the
> > matplotlib dashboard is on mdboom's account.
>
> I have the option of clicking "add a project" and then selecting
> github / numpy / numpy from the list, but AFAICT this seems to create
> a second independent copy of the project in appveyor's system, which
> I'm pretty sure is not what we want?
>
> The interface is extraordinarily confusing. They really need to hire
> an editor for their docs / messages :-(
>
> (It's also astonishingly slow -- like 30 minutes per build, and builds
> run in serial...)
>

The Python 3 build runs much faster than the Python 2. You can close and
reopen my testing PR to check what happens if you enable the numpy project.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Nathaniel Smith]

On Dec 20, 2015 12:45 PM, "Ralf Gommers"  wrote:
>
>
>
> On Sun, Dec 20, 2015 at 9:34 PM, Nathaniel Smith  wrote:
>
>> On Dec 20, 2015 12:23 PM, "Ralf Gommers"  wrote:
>> >
>> >
>> >
>> > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <
ralf.gomm...@gmail.com> wrote:
>> 
>> 
>> 
>>  On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>> >
>> > Hi All,
>> >
>> > Just checking if someone has already registered numpy on appveyor.
If not, I intend to rename my personal account. Note that as AFAICT,
someone has to be the admin for appveyor, and that someone, like everyone
else, can only have one account on appveyor.
>> 
>> 
>>  Don't think so, unless they changed something very recently. I have
already registered 2 accounts (my own, and pywavelets).
>> >>>
>> >>>
>> >>> I get
>> >>>
>> >>> AppVeyor user with specified email already exists.
>> >>>
>> >>> This seems to have been the case since at least mid summer. When did
you register the accounts?
>> >>
>> >>
>> >> Did you use different email addresses?
>> >
>> >
>> > No, it looks like you can sign in with your Github login, and with
email + password. Those can be different.
>>
>> I wonder if there's a better way to organize these kinds of things in
general? It's probably not a big deal, but it can eventually make a mess
sometimes if there's only one person who has access to some piece of
critical infrastructure, and then years later they aren't available at some
point or no one knows who to ask. If we had the steering council mailing
list set up we could use that for the mailing address, but of course atm we
don't. Or we could make a scratch email account somewhere
(numpy-accounts@gmail) and pass around the login credentials. Or ask Leah
at numfocus to make an account and then add us as admins. Or maybe this is
overthinking it and we should just use some hack and move on :-)
>
>
> I like the mailing list idea. Why not set up the steering council list
now? It's not like that's a lot of work.

The work is in convincing the one person (that I know about) who has access
to the appropriate permissions to pay attention to my email... I've made
several attempts at getting this set up with no effect so far :-/ But yeah,
it does need to be done in any case so I'll try again.

-n
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Nathaniel Smith]

On Sun, Dec 20, 2015 at 7:34 PM, Charles R Harris
 wrote:
>
>
> On Sun, Dec 20, 2015 at 8:11 PM, Nathaniel Smith  wrote:
>>
>> On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris
>>  wrote:
[...]
>> > Nathaniel, if you have an appveyor account that lets you have access to
>> > the
>> > numpy repo, could you try enabling it and see what happens? I note the
>> > matplotlib dashboard is on mdboom's account.
>>
>> I have the option of clicking "add a project" and then selecting
>> github / numpy / numpy from the list, but AFAICT this seems to create
>> a second independent copy of the project in appveyor's system, which
>> I'm pretty sure is not what we want?
>
>
> Do you mean that we ended up with double the appveyor testing, one for each
> of our accounts? The process you describe is what I did.

Yes, exactly. Pretty useless. I let it run a few builds, and then
deleted it again...

-n

-- 
Nathaniel J. Smith -- http://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

> The work is in convincing the one person (that I know about) who has
access to the appropriate permissions to pay attention to my email... I've
made several attempts at getting this set up with no effect so far :-/ But
yeah, it does need to be done in any case so I'll try again.

I tried simple and dumb, just enabled the numpy repository from my personal
appveyor account. A test PR shows both travis and appveyor running. Now,
that may be just for my PRs, so can someone else try a test PR and see if
the tests run?

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 8:11 PM, Nathaniel Smith  wrote:

> On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris
>  wrote:
> >
> >
> > On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith  wrote:
> >>
> [...]
> >> Also, am I correct that these are win64 builds only? Anyone know if it
> >> would be easy to add win32?
> >
> >
> > Don't know. I also noticed a bunch of permission errors with temp files.
> > There are some failing tests that are filtered out with our preliminary
> > appveyor script.
>
> Yeah, looking at the logs for
>
> https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/9lkl8940dvhrml2v
>
> https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/awgp7fnne15jwb21
> there appears to be some configuration weirdness that makes temp files
> unwriteable so all the tests that use those fail, plus some mysterious
> issue with distutils.msvc9compiler, plus what's probably a genuine
> error in mtrand.pyx where it is expecting 'long' to be 64 bits (which
> it is on every 64-bit platform we support *except* for win64), plus
> what's probably a genuine problem with test_diophantine_fuzz (py3 only
> -- maybe some PyInt/PyLong transition issue?).
>
> > Nathaniel, if you have an appveyor account that lets you have access to
> the
> > numpy repo, could you try enabling it and see what happens? I note the
> > matplotlib dashboard is on mdboom's account.
>
> I have the option of clicking "add a project" and then selecting
> github / numpy / numpy from the list, but AFAICT this seems to create
> a second independent copy of the project in appveyor's system, which
> I'm pretty sure is not what we want?
>

Do you mean that we ended up with double the appveyor testing, one for each
of our accounts? The process you describe is what I did.


>
> The interface is extraordinarily confusing. They really need to hire
> an editor for their docs / messages :-(
>
>
Yes, they do.


> (It's also astonishingly slow -- like 30 minutes per build, and builds
> run in serial...)
>
>
There is that.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Nathaniel Smith]

On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris
 wrote:
>
>
> On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith  wrote:
>>
[...]
>> Also, am I correct that these are win64 builds only? Anyone know if it
>> would be easy to add win32?
>
>
> Don't know. I also noticed a bunch of permission errors with temp files.
> There are some failing tests that are filtered out with our preliminary
> appveyor script.

Yeah, looking at the logs for
  https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/9lkl8940dvhrml2v
  https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/awgp7fnne15jwb21
there appears to be some configuration weirdness that makes temp files
unwriteable so all the tests that use those fail, plus some mysterious
issue with distutils.msvc9compiler, plus what's probably a genuine
error in mtrand.pyx where it is expecting 'long' to be 64 bits (which
it is on every 64-bit platform we support *except* for win64), plus
what's probably a genuine problem with test_diophantine_fuzz (py3 only
-- maybe some PyInt/PyLong transition issue?).

> Nathaniel, if you have an appveyor account that lets you have access to the
> numpy repo, could you try enabling it and see what happens? I note the
> matplotlib dashboard is on mdboom's account.

I have the option of clicking "add a project" and then selecting
github / numpy / numpy from the list, but AFAICT this seems to create
a second independent copy of the project in appveyor's system, which
I'm pretty sure is not what we want?

The interface is extraordinarily confusing. They really need to hire
an editor for their docs / messages :-(

(It's also astonishingly slow -- like 30 minutes per build, and builds
run in serial...)

-n

-- 
Nathaniel J. Smith -- http://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
wrote:

>
>
> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> Hi All,
>>
>> Just checking if someone has already registered numpy on appveyor. If
>> not, I intend to rename my personal account. Note that as AFAICT, someone
>> has to be the admin for appveyor, and that someone, like everyone else, can
>> only have one account on appveyor.
>>
>
> Don't think so, unless they changed something very recently. I have
> already registered 2 accounts (my own, and pywavelets).
>

I created my appveyor account with the github button, that may be the
problem. Ralf, did you use that button, or did you create all your accounts
with the name/email/password method?

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith  wrote:

> On Sun, Dec 20, 2015 at 4:11 PM, Charles R Harris
>  wrote:
> >
> >
> >
> > On Sun, Dec 20, 2015 at 4:27 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >>
> >>
> >>
> >> On Sun, Dec 20, 2015 at 4:22 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >>>
> >>> 
> >>>
> >>> > The work is in convincing the one person (that I know about) who has
> access to the appropriate permissions to pay attention to my email... I've
> made several attempts at getting this set up with no effect so far :-/ But
> yeah, it does need to be done in any case so I'll try again.
> >>>
> >>> I tried simple and dumb, just enabled the numpy repository from my
> personal appveyor account. A test PR shows both travis and appveyor
> running. Now, that may be just for my PRs, so can someone else try a test
> PR and see if the tests run?
> >>>
> >>
> >> PS, you need to base on current master.
> >
> >
> > And added an AppVeyor team to the numpy organization as suggested here.
> Shrug, I don't know if it makes any difference, but you can add yourself.
>
> For those following along at home, the build dashboard appears to be here:
>   https://ci.appveyor.com/project/charris/numpy
>
> And IIUC, anyone who adds themselves (or asks one of us to add them)
> to the AppVeyor team here:
>
>   https://github.com/orgs/numpy/teams
>
> should get some sort of permissions to mess with the AppVeyor builds.
> Except I did that but it doesn't seem to have done anything. Maybe
> AppVeyor will resync with github at some point and it will start doing
> something.
>
> Also, am I correct that these are win64 builds only? Anyone know if it
> would be easy to add win32?
>

Don't know. I also noticed a bunch of permission errors with temp files.
There are some failing tests that are filtered out with our preliminary
appveyor script.

Nathaniel, if you have an appveyor account that lets you have access to the
numpy repo, could you try enabling it and see what happens? I note the
matplotlib dashboard is on mdboom's account.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 4:22 PM, Charles R Harris  wrote:

> 
>
> > The work is in convincing the one person (that I know about) who has
> access to the appropriate permissions to pay attention to my email... I've
> made several attempts at getting this set up with no effect so far :-/ But
> yeah, it does need to be done in any case so I'll try again.
>
> I tried simple and dumb, just enabled the numpy repository from my
> personal appveyor account. A test PR shows both travis and appveyor
> running. Now, that may be just for my PRs, so can someone else try a test
> PR and see if the tests run?
>
>
PS, you need to base on current master.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Nathaniel Smith]

On Sun, Dec 20, 2015 at 4:11 PM, Charles R Harris
 wrote:
>
>
>
> On Sun, Dec 20, 2015 at 4:27 PM, Charles R Harris  
> wrote:
>>
>>
>>
>> On Sun, Dec 20, 2015 at 4:22 PM, Charles R Harris 
>>  wrote:
>>>
>>> 
>>>
>>> > The work is in convincing the one person (that I know about) who has 
>>> > access to the appropriate permissions to pay attention to my email... 
>>> > I've made several attempts at getting this set up with no effect so far 
>>> > :-/ But yeah, it does need to be done in any case so I'll try again.
>>>
>>> I tried simple and dumb, just enabled the numpy repository from my personal 
>>> appveyor account. A test PR shows both travis and appveyor running. Now, 
>>> that may be just for my PRs, so can someone else try a test PR and see if 
>>> the tests run?
>>>
>>
>> PS, you need to base on current master.
>
>
> And added an AppVeyor team to the numpy organization as suggested here. 
> Shrug, I don't know if it makes any difference, but you can add yourself.

For those following along at home, the build dashboard appears to be here:
  https://ci.appveyor.com/project/charris/numpy

And IIUC, anyone who adds themselves (or asks one of us to add them)
to the AppVeyor team here:

  https://github.com/orgs/numpy/teams

should get some sort of permissions to mess with the AppVeyor builds.
Except I did that but it doesn't seem to have done anything. Maybe
AppVeyor will resync with github at some point and it will start doing
something.

Also, am I correct that these are win64 builds only? Anyone know if it
would be easy to add win32?

-n

-- 
Nathaniel J. Smith -- http://vorpus.org
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
wrote:

>
>
> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> Hi All,
>>
>> Just checking if someone has already registered numpy on appveyor. If
>> not, I intend to rename my personal account. Note that as AFAICT, someone
>> has to be the admin for appveyor, and that someone, like everyone else, can
>> only have one account on appveyor.
>>
>
> Don't think so, unless they changed something very recently. I have
> already registered 2 accounts (my own, and pywavelets).
>

I get

AppVeyor user with specified email already exists.

This seems to have been the case since at least mid summer. When did you
register the accounts?


>
>
>> Other folks with accounts can be added as collaborators, but they cannot
>> belong to the numpy account. Or something. Reading the appveyor
>> documentation, such as it is, is like driving through a heavy fog and the
>> user interface is lacking. I would be happy for any input here.
>>
>
> Yeah, it's not the most friendly interface. I think you can just go to
> https://ci.appveyor.com/signup and register an account "numpy" with your
> email and it probably won't complain that you already have charris
> registered with the same email account attached.
>
> Ralf
>
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] AppVeyor

[Charles R Harris]

Hi All,

Just checking if someone has already registered numpy on appveyor. If not,
I intend to rename my personal account. Note that as AFAICT, someone has to
be the admin for appveyor, and that someone, like everyone else, can only
have one account on appveyor. Other folks with accounts can be added as
collaborators, but they cannot belong to the numpy account. Or something.
Reading the appveyor documentation, such as it is, is like driving through
a heavy fog and the user interface is lacking. I would be happy for any
input here.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ralf Gommers]

On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris  wrote:

> Hi All,
>
> Just checking if someone has already registered numpy on appveyor. If not,
> I intend to rename my personal account. Note that as AFAICT, someone has to
> be the admin for appveyor, and that someone, like everyone else, can only
> have one account on appveyor.
>

Don't think so, unless they changed something very recently. I have already
registered 2 accounts (my own, and pywavelets).


> Other folks with accounts can be added as collaborators, but they cannot
> belong to the numpy account. Or something. Reading the appveyor
> documentation, such as it is, is like driving through a heavy fog and the
> user interface is lacking. I would be happy for any input here.
>

Yeah, it's not the most friendly interface. I think you can just go to
https://ci.appveyor.com/signup and register an account "numpy" with your
email and it probably won't complain that you already have charris
registered with the same email account attached.

Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ralf Gommers]

On Sun, Dec 20, 2015 at 9:34 PM, Nathaniel Smith  wrote:

On Dec 20, 2015 12:23 PM, "Ralf Gommers"  wrote:
> >
> >
> >
> > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >>
> >>
> >>
> >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >>>
> >>>
> >>>
> >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
> wrote:
> 
> 
> 
>  On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
> >
> > Hi All,
> >
> > Just checking if someone has already registered numpy on appveyor.
> If not, I intend to rename my personal account. Note that as AFAICT,
> someone has to be the admin for appveyor, and that someone, like everyone
> else, can only have one account on appveyor.
> 
> 
>  Don't think so, unless they changed something very recently. I have
> already registered 2 accounts (my own, and pywavelets).
> >>>
> >>>
> >>> I get
> >>>
> >>> AppVeyor user with specified email already exists.
> >>>
> >>> This seems to have been the case since at least mid summer. When did
> you register the accounts?
> >>
> >>
> >> Did you use different email addresses?
> >
> >
> > No, it looks like you can sign in with your Github login, and with email
> + password. Those can be different.
>
> I wonder if there's a better way to organize these kinds of things in
> general? It's probably not a big deal, but it can eventually make a mess
> sometimes if there's only one person who has access to some piece of
> critical infrastructure, and then years later they aren't available at some
> point or no one knows who to ask. If we had the steering council mailing
> list set up we could use that for the mailing address, but of course atm we
> don't. Or we could make a scratch email account somewhere
> (numpy-accounts@gmail) and pass around the login credentials. Or ask Leah
> at numfocus to make an account and then add us as admins. Or maybe this is
> overthinking it and we should just use some hack and move on :-)
>

I like the mailing list idea. Why not set up the steering council list now?
It's not like that's a lot of work.
Asking Numfocus doesn't make sense for this.

Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 1:23 PM, Ralf Gommers 
wrote:

>
>
> On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>>>
>>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
>>> wrote:
>>>


 On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
 charlesr.har...@gmail.com> wrote:

> Hi All,
>
> Just checking if someone has already registered numpy on appveyor. If
> not, I intend to rename my personal account. Note that as AFAICT, someone
> has to be the admin for appveyor, and that someone, like everyone else, 
> can
> only have one account on appveyor.
>

 Don't think so, unless they changed something very recently. I have
 already registered 2 accounts (my own, and pywavelets).

>>>
>>> I get
>>>
>>> AppVeyor user with specified email already exists.
>>>
>>> This seems to have been the case since at least mid summer. When did you
>>> register the accounts?
>>>
>>
>> Did you use different email addresses?
>>
>
> No, it looks like you can sign in with your Github login, and with email +
> password. Those can be different.
>

Doesn't work. Signing in with github is me, not numpy. I do get the option
of adding numpy/numpy, but that isn't the same.

Maybe cleaning out all those darn cookies will help.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:

>
>
> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
> wrote:
>
>>
>>
>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> Just checking if someone has already registered numpy on appveyor. If
>>> not, I intend to rename my personal account. Note that as AFAICT, someone
>>> has to be the admin for appveyor, and that someone, like everyone else, can
>>> only have one account on appveyor.
>>>
>>
>> Don't think so, unless they changed something very recently. I have
>> already registered 2 accounts (my own, and pywavelets).
>>
>
> I get
>
> AppVeyor user with specified email already exists.
>
> This seems to have been the case since at least mid summer. When did you
> register the accounts?
>

Did you use different email addresses?



Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Ralf Gommers]

On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris  wrote:

>
>
> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
>> wrote:
>>
>>>
>>>
>>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
>>> charlesr.har...@gmail.com> wrote:
>>>
 Hi All,

 Just checking if someone has already registered numpy on appveyor. If
 not, I intend to rename my personal account. Note that as AFAICT, someone
 has to be the admin for appveyor, and that someone, like everyone else, can
 only have one account on appveyor.

>>>
>>> Don't think so, unless they changed something very recently. I have
>>> already registered 2 accounts (my own, and pywavelets).
>>>
>>
>> I get
>>
>> AppVeyor user with specified email already exists.
>>
>> This seems to have been the case since at least mid summer. When did you
>> register the accounts?
>>
>
> Did you use different email addresses?
>

No, it looks like you can sign in with your Github login, and with email +
password. Those can be different.

Ralf
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Nathaniel Smith]

On Dec 20, 2015 12:23 PM, "Ralf Gommers"  wrote:
>
>
>
> On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>>
>>
>>
>> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>>>
>>>
>>>
>>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers 
wrote:



 On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>
> Hi All,
>
> Just checking if someone has already registered numpy on appveyor. If
not, I intend to rename my personal account. Note that as AFAICT, someone
has to be the admin for appveyor, and that someone, like everyone else, can
only have one account on appveyor.


 Don't think so, unless they changed something very recently. I have
already registered 2 accounts (my own, and pywavelets).
>>>
>>>
>>> I get
>>>
>>> AppVeyor user with specified email already exists.
>>>
>>> This seems to have been the case since at least mid summer. When did
you register the accounts?
>>
>>
>> Did you use different email addresses?
>
>
> No, it looks like you can sign in with your Github login, and with email
+ password. Those can be different.

I wonder if there's a better way to organize these kinds of things in
general? It's probably not a big deal, but it can eventually make a mess
sometimes if there's only one person who has access to some piece of
critical infrastructure, and then years later they aren't available at some
point or no one knows who to ask. If we had the steering council mailing
list set up we could use that for the mailing address, but of course atm we
don't. Or we could make a scratch email account somewhere
(numpy-accounts@gmail) and pass around the login credentials. Or ask Leah
at numfocus to make an account and then add us as admins. Or maybe this is
overthinking it and we should just use some hack and move on :-)

-n
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] AppVeyor

[Charles R Harris]

On Sun, Dec 20, 2015 at 1:45 PM, Ralf Gommers 
wrote:

>
>
> On Sun, Dec 20, 2015 at 9:34 PM, Nathaniel Smith  wrote:
>
> On Dec 20, 2015 12:23 PM, "Ralf Gommers"  wrote:
>> >
>> >
>> >
>> > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <
>> ralf.gomm...@gmail.com> wrote:
>> 
>> 
>> 
>>  On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>> >
>> > Hi All,
>> >
>> > Just checking if someone has already registered numpy on appveyor.
>> If not, I intend to rename my personal account. Note that as AFAICT,
>> someone has to be the admin for appveyor, and that someone, like everyone
>> else, can only have one account on appveyor.
>> 
>> 
>>  Don't think so, unless they changed something very recently. I have
>> already registered 2 accounts (my own, and pywavelets).
>> >>>
>> >>>
>> >>> I get
>> >>>
>> >>> AppVeyor user with specified email already exists.
>> >>>
>> >>> This seems to have been the case since at least mid summer. When did
>> you register the accounts?
>> >>
>> >>
>> >> Did you use different email addresses?
>> >
>> >
>> > No, it looks like you can sign in with your Github login, and with
>> email + password. Those can be different.
>>
>> I wonder if there's a better way to organize these kinds of things in
>> general? It's probably not a big deal, but it can eventually make a mess
>> sometimes if there's only one person who has access to some piece of
>> critical infrastructure, and then years later they aren't available at some
>> point or no one knows who to ask. If we had the steering council mailing
>> list set up we could use that for the mailing address, but of course atm we
>> don't. Or we could make a scratch email account somewhere
>> (numpy-accounts@gmail) and pass around the login credentials. Or ask
>> Leah at numfocus to make an account and then add us as admins. Or maybe
>> this is overthinking it and we should just use some hack and move on :-)
>>
>
> I like the mailing list idea. Why not set up the steering council list
> now? It's not like that's a lot of work.
> Asking Numfocus doesn't make sense for this.
>

Appveyor recommends the name/mailing address/password registration for
projects. Do we have an office vault for the password ;)

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Chris Barker]

On Thu, Mar 5, 2015 at 5:07 PM, Charles R Harris charlesr.har...@gmail.com
wrote:

 Do line endings in the scripts matter?


I have no idea if powershell cares about line endings, but if you are using
git, then you'll want to make sure that your repo is properly configured to
normalize line endings -- then there should be no problems. And you realy
want that anyway for any multi-platform project.

-CHB

-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/ORR(206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115   (206) 526-6317   main reception

chris.bar...@noaa.gov
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Denis-Alexander Engemann]

Same for MNE-Python:

https://github.com/mne-tools/mne-python/blob/master/appveyor.yml

Denis

2015-03-05 20:42 GMT+01:00 Stefan van der Walt stef...@berkeley.edu:

 Hi Chuck

 On 2015-03-05 10:09:08, Charles R Harris
 charlesr.har...@gmail.com wrote:
  Anyone familiar with appveyor http://www.appveyor.com/? Is
  this something we could use to test/build numpy on windows
  machines? It is free for open source.

 We already use this for scikit-image, and you are welcome to grab
 the setup here:

 https://github.com/scikit-image/scikit-image/blob/master/appveyor.yml

 GitHub now also supports multiple status reporting out of the box:


 https://github.com/blog/1935-see-results-from-all-pull-request-status-checks

 Stéfan
 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion

___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Stefan van der Walt]

Hi Chuck

On 2015-03-05 10:09:08, Charles R Harris 
charlesr.har...@gmail.com wrote:
 Anyone familiar with appveyor http://www.appveyor.com/? Is 
 this something we could use to test/build numpy on windows 
 machines? It is free for open source.

We already use this for scikit-image, and you are welcome to grab 
the setup here:

https://github.com/scikit-image/scikit-image/blob/master/appveyor.yml

GitHub now also supports multiple status reporting out of the box: 

https://github.com/blog/1935-see-results-from-all-pull-request-status-checks

Stéfan
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Charles R Harris]

On Thu, Mar 5, 2015 at 12:42 PM, Stefan van der Walt stef...@berkeley.edu
wrote:

 Hi Chuck

 On 2015-03-05 10:09:08, Charles R Harris
 charlesr.har...@gmail.com wrote:
  Anyone familiar with appveyor http://www.appveyor.com/? Is
  this something we could use to test/build numpy on windows
  machines? It is free for open source.

 We already use this for scikit-image, and you are welcome to grab
 the setup here:

 https://github.com/scikit-image/scikit-image/blob/master/appveyor.yml

 GitHub now also supports multiple status reporting out of the box:


 https://github.com/blog/1935-see-results-from-all-pull-request-status-checks


Thanks. Anything tricky about setting up an appveyor account?

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Robert McGibbon]

I develop on linux and osx, and I haven't experienced any Appveyor problems
related to line endings, so I assume it's normalized somehow.

-Robert
On Mar 5, 2015 5:08 PM, Charles R Harris charlesr.har...@gmail.com
wrote:



 On Thu, Mar 5, 2015 at 5:38 PM, Robert McGibbon rmcgi...@gmail.com
 wrote:

 From my experience, it's pretty easy, assuming you're prepared to pick up
 some powershell.
 Some useful resources are

  - Olivier Grisel's example.
 https://github.com/ogrisel/python-appveyor-demo
  - I made a similar example, using conda.
 https://github.com/rmcgibbo/python-appveyor-conda-example

 One problem is that appveyor is often quite slow compared to TravisCI, so
 this can be a little annoying. But it's better than nothing.


 Do line endings in the scripts matter?

 Chuck


 ___
 NumPy-Discussion mailing list
 NumPy-Discussion@scipy.org
 http://mail.scipy.org/mailman/listinfo/numpy-discussion


___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] appveyor CI

[Charles R Harris]

Anyone familiar with appveyor http://www.appveyor.com/? Is this something
we could use to test/build numpy on windows machines? It is free for open
source.

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Robert McGibbon]

From my experience, it's pretty easy, assuming you're prepared to pick up
some powershell.
Some useful resources are

 - Olivier Grisel's example.
https://github.com/ogrisel/python-appveyor-demo
 - I made a similar example, using conda.
https://github.com/rmcgibbo/python-appveyor-conda-example

One problem is that appveyor is often quite slow compared to TravisCI, so
this can be a little annoying. But it's better than nothing.

-Robert
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] appveyor CI

[Charles R Harris]

On Thu, Mar 5, 2015 at 5:38 PM, Robert McGibbon rmcgi...@gmail.com wrote:

 From my experience, it's pretty easy, assuming you're prepared to pick up
 some powershell.
 Some useful resources are

  - Olivier Grisel's example.
 https://github.com/ogrisel/python-appveyor-demo
  - I made a similar example, using conda.
 https://github.com/rmcgibbo/python-appveyor-conda-example

 One problem is that appveyor is often quite slow compared to TravisCI, so
 this can be a little annoying. But it's better than nothing.


Do line endings in the scripts matter?

Chuck
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion