I didn't know we had this, I'll get on this now.
Can we add this to our merge checks?
We intentionally didn't because it'd slow down merges
@dhermes, if I could get on the email list for this and the docs when they fail that would be awesome.
Also, is there a way to flush the cache for appveyor?
I took a quick peek at https://ci.appveyor.com/project/dhermes/gcloud-python/settings/permissions and can't figure out how to get you added. (No bandwidth to play around right now.) Can you find out how and help me click my way along?
@dhermes, I think this will get you closer.
http://www.appveyor.com/docs/team-setup
I think you can just go to https://ci.appveyor.com/team and add me as a _collaborator_ I believe.
I signed up for Appveyor with my github account so I should be in there somewhere.

Oh sorry! My github account email it used was [email protected]. Not sure why it used that one over the one you have there though? This might be my default one.
OK added you
Thanks! I don't see gcloud-python in my projects list but maybe it takes a bit.
Looks like you might need to add permissions on a per project basis.
https://www.appveyor.com/docs/team-setup#permissions
Permissions can be defined on project level and limit user access to that particular project. Project-level permission has three states: Allow, Deny and Inherit. "Inherit" means applying permissions defined on role level. Both "Allow" and "Deny" overrides permissions defined on role level.
@dhermes, I can't restart the appveyor builds for some reason.
It looks like something might have gotten updated? Hard to tell from this comment.
https://github.com/grpc/grpc/issues/6939#issuecomment-226720519
Permissions seem fine by default:

I think it must be some kind of cross github permissions that's not letting
the projects show up in my projects list on appveyor.
I added the gcloud-python project manually and I'll try and build though.
https://ci.appveyor.com/project/daspecster/gcloud-python
On Fri, Jun 17, 2016 at 1:36 PM, Danny Hermes [email protected]
wrote:
Permissions seem fine
https://ci.appveyor.com/project/dhermes/gcloud-python/settings/permissions
by default:[image: screen shot 2016-06-17 at 10 36 17 am]
https://cloud.githubusercontent.com/assets/520669/16159401/67415c76-3477-11e6-9591-c6d73beaa5b3.png—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-python/issues/1863#issuecomment-226832985,
or mute the thread
https://github.com/notifications/unsubscribe/AALvyCuHyW0akdMZ2W8mhXv9mRtgFJrHks5qMts6gaJpZM4I3hW4
.
Tom Schultz
SGTM
Still failing grpcio
https://ci.appveyor.com/project/daspecster/gcloud-python
@bjwatson, did you guys have any more ideas on this?
_All_ the environments are failing, not just the 2.7 ones (the only ones where grpcio is wired in).
@daspecster, @dhermes Note that Danny's Appveyor builds have been failing since the 0.14.1 release.
I'll try and find a fix for this permissions issue. Looks like people run into that a little bit on appveyor.
@daspecster I already added a fix for tempfiles in a previous commit. Trying to track now
Awesome thanks @dhermes!
I queued up a build using your _NamedTemporaryFile helper.
https://ci.appveyor.com/project/daspecster/gcloud-python-utjkc
@daspecster No new ideas, apart from what's already been expressed in https://github.com/grpc/grpc/issues/6939. I did realize today that this issue applies to all recent versions of grpcio: 0.13.0, 0.13.1, and 0.14.0.
Is this the first time we had a grpcio dependency in the grpc-google-* and gax-google-* packages that we are attempting to use on AppVeyor and ReadTheDocs?
Yeah @tseaver mentioned above that it looks like it's been happening for a little while.
@bjwatson We just merged #1815, making grcpio an unconditional dependency of gcloud on Python 2.7: prior to the merge, users had to request installing the gcloud[grpc] extra dependency to get it.
@daspecster the other failures post 0.14.1 weren't related to grpcio.
Ah ok, sorry I'm jumbling things up I guess.
On Friday, June 17, 2016, Tres Seaver [email protected] wrote:
@bjwatson https://github.com/bjwatson We just merged #1815
https://github.com/GoogleCloudPlatform/gcloud-python/pull/1815, making
grcpio an unconditional dependency of gcloud on Python 2.7: prior to the
merge, users had to request installing the gcloud[grpc] extra dependency
to get it.@daspecster https://github.com/daspecster the other failures post
0.14.1 weren't related to grpcio.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-python/issues/1863#issuecomment-226909849,
or mute the thread
https://github.com/notifications/unsubscribe/AALvyNFu5fnZFMXRaE54LshLQ46iBztPks5qMzqdgaJpZM4I3hW4
.
Tom Schultz
@daspecster It's still failing: https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.428.master
Is there a way to get around the grpcio issue that you know of?
@daspecster If Appveyor sets a known environment variable, we could use it to avoid adding the GRPC_EXTRAS requirements to install_requires.
I think it sets an APPVEYOR envar to true (https://www.appveyor.com/docs/environment-variables).
So grpcio doesn't work on Windows? Isn't that a huge problem @jgeewax?
@dhermes it appears to be an oddity with installation through a dependency. Maybe we could work around it by pre-installing grpcio under Appveyor?
Is this issue fixed, or is it still outstanding? I saw that https://github.com/grpc/grpc/issues/6939 was closed and will be fixed in 0.15.0.
@bjwatson, I don't think 0.15.0 has been released yet to try it. Do you know when it might get released?
@daspecster I asked on the grpc ticket.
Does the force install patches that @tseaver merged provide a decent work-around for now?
@bjwatson, I _think_ it just pulls from pypi.
https://github.com/GoogleCloudPlatform/gcloud-python/blob/master/appveyor.yml#L77
@daspecster 0.15.0 will be probably be published sometime next week
That said, it looks like we will soon need to move away from egg-info dependencies, unless we have a really good reason for needing them: https://github.com/grpc/grpc/issues/6989
Still getting b0rken emails:
https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.443.bigtable-v2
https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.447.logging-stdlib-handler-feature
https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.451.bigtable-v2
https://ci.appveyor.com/project/dhermes/gcloud-python/build/1.0.453.master
Looks like the errors have changed since the gRPC 0.15.0 release last night.
Looks as though protobuf is not getting installed. Since gcloud explicitly depends on it, I don't know how that can happen.
I don't know if this helps in this case, but last week I set up the gax-python repo to install (and cache) a protobuf installation for testing with proto messages (fix for https://github.com/GoogleCloudPlatform/gcloud-python/issues/1869):
Also, I'm going to build some new versions of google-gax, grpc-google-(pubsub|logging), and gax-google-(pubsub|logging) with grpc 0.15.0 and protobuf v3.0.0-beta-3.1 to see if that helps.
I have built and published google-gax 0.12.2 and version 0.7.11 of the Pub/Sub and Logging packages
This is fixed by a series of changes e.g. https://github.com/googleapis/gax-python/pull/120 and https://github.com/grpc/grpc/issues/7528