-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Travis Builds breaking due boto==2.49.0 trying to import google_compute_engine #1771
Comments
Possibly related? Maybe this is happening because TravisCi is behind the scenes running on google cloud? |
Okay, I see this I guess I have to do the same if I'm running a build on travis. If this isn't in your README or docs somewhere yet, it might be helpful to shout it out. This is a very wierd bug. Have you considered just dropping support for boto? 😆 |
* Update aws line item aggregate table test to use defined dates * Trying the suggestion from the github issue getmoto/moto#1771
I think you are right that this is mostly a boto issue. I don't have a great place in the docs or README to add this, but hopefully people will find this issue going forward. |
This is using the fix as mentioned in getmoto/moto#1771
* See why on getmoto/moto#1771
* See why on getmoto/moto#1771
* See why on getmoto/moto#1771
It's a workaround for this issue: getmoto/moto#1771
It's a workaround for this issue: getmoto/moto#1771
…ct-koku#220) * Update aws line item aggregate table test to use defined dates * Trying the suggestion from the github issue getmoto/moto#1771
…ct-koku#220) * Update aws line item aggregate table test to use defined dates * Trying the suggestion from the github issue getmoto/moto#1771
Reporting Bugs
Using
moto==1.3.4
My pytest output in TravisCI is the following:
It's really strange that it all of a sudden tries to lookup this google_compute_engine module out of python2.7 folder.
Upstream boto problem? I could try to pin my boto dependency to ==2.45.0 and see if it works.
Thanks for any help.
The text was updated successfully, but these errors were encountered: