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
On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
Don't think so, unless they changed something very recently. I have already registered 2 accounts (my own, and pywavelets).
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
On Dec 20, 2015 12:23 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: > > > > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris < charlesr.harris@gmail.com> wrote: >> >> >> >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris < charlesr.harris@gmail.com> wrote: >>> >>> >>> >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote: >>>> >>>> >>>> >>>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris < charlesr.harris@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
On Sun, Dec 20, 2015 at 9:34 PM, Nathaniel Smith <njs@pobox.com> wrote: On Dec 20, 2015 12:23 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: > > > > > > > > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris < > charlesr.harris@gmail.com> wrote: > >> > >> > >> > >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris < > charlesr.harris@gmail.com> wrote: > >>> > >>> > >>> > >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <ralf.gommers@gmail.com> > wrote: > >>>> > >>>> > >>>> > >>>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris < > charlesr.harris@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
On Dec 20, 2015 12:45 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote:
charlesr.harris@gmail.com> wrote: 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
On Sun, Dec 20, 2015 at 4:27 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
And added an AppVeyor team to the numpy organization as suggested here <http://www.appveyor.com/docs/team-setup#github-teams>. Shrug, I don't know if it makes any difference, but you can add yourself. Chuck
On Sun, Dec 20, 2015 at 4:11 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
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
On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith <njs@pobox.com> wrote:
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
On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith <njs@pobox.com> wrote:
[...]
Yeah, looking at the logs for https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/9lkl8940dvhrml... https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/awgp7fnne15jwb... 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?).
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
On Sun, Dec 20, 2015 at 8:11 PM, Nathaniel Smith <njs@pobox.com> wrote:
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
On Sun, Dec 20, 2015 at 7:34 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
[...]
Yes, exactly. Pretty useless. I let it run a few builds, and then deleted it again... -n -- Nathaniel J. Smith -- http://vorpus.org
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
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
On Mon, Dec 21, 2015 at 7:42 PM, Ian Henriksen < insertinterestingnamehere@gmail.com> 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? Ralf <https://mail.scipy.org/mailman/listinfo/numpy-discussion>
On Tue, Dec 22, 2015 at 12:14 AM Ralf Gommers <ralf.gommers@gmail.com> 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
On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
Don't think so, unless they changed something very recently. I have already registered 2 accounts (my own, and pywavelets).
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
On Dec 20, 2015 12:23 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: > > > > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris < charlesr.harris@gmail.com> wrote: >> >> >> >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris < charlesr.harris@gmail.com> wrote: >>> >>> >>> >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <ralf.gommers@gmail.com> wrote: >>>> >>>> >>>> >>>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris < charlesr.harris@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
On Sun, Dec 20, 2015 at 9:34 PM, Nathaniel Smith <njs@pobox.com> wrote: On Dec 20, 2015 12:23 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: > > > > > > > > On Sun, Dec 20, 2015 at 8:23 PM, Charles R Harris < > charlesr.harris@gmail.com> wrote: > >> > >> > >> > >> On Sun, Dec 20, 2015 at 11:08 AM, Charles R Harris < > charlesr.harris@gmail.com> wrote: > >>> > >>> > >>> > >>> On Sun, Dec 20, 2015 at 10:48 AM, Ralf Gommers <ralf.gommers@gmail.com> > wrote: > >>>> > >>>> > >>>> > >>>> On Sun, Dec 20, 2015 at 6:31 PM, Charles R Harris < > charlesr.harris@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
On Dec 20, 2015 12:45 PM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote:
charlesr.harris@gmail.com> wrote: 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
On Sun, Dec 20, 2015 at 4:27 PM, Charles R Harris <charlesr.harris@gmail.com
wrote:
And added an AppVeyor team to the numpy organization as suggested here <http://www.appveyor.com/docs/team-setup#github-teams>. Shrug, I don't know if it makes any difference, but you can add yourself. Chuck
On Sun, Dec 20, 2015 at 4:11 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
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
On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith <njs@pobox.com> wrote:
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
On Sun, Dec 20, 2015 at 6:43 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sun, Dec 20, 2015 at 5:48 PM, Nathaniel Smith <njs@pobox.com> wrote:
[...]
Yeah, looking at the logs for https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/9lkl8940dvhrml... https://ci.appveyor.com/project/charris/numpy/build/1.0.5/job/awgp7fnne15jwb... 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?).
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
On Sun, Dec 20, 2015 at 8:11 PM, Nathaniel Smith <njs@pobox.com> wrote:
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
On Sun, Dec 20, 2015 at 7:34 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
[...]
Yes, exactly. Pretty useless. I let it run a few builds, and then deleted it again... -n -- Nathaniel J. Smith -- http://vorpus.org
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
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
On Mon, Dec 21, 2015 at 7:42 PM, Ian Henriksen < insertinterestingnamehere@gmail.com> 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? Ralf <https://mail.scipy.org/mailman/listinfo/numpy-discussion>
On Tue, Dec 22, 2015 at 12:14 AM Ralf Gommers <ralf.gommers@gmail.com> 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
participants (4)
-
Charles R Harris -
Ian Henriksen -
Nathaniel Smith -
Ralf Gommers