Skip to content
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

testing: pip install failed in py-3.8 build #3677

Closed
tmatsuo opened this issue May 4, 2020 · 0 comments · Fixed by #3679
Closed

testing: pip install failed in py-3.8 build #3677

tmatsuo opened this issue May 4, 2020 · 0 comments · Fixed by #3679
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. testing type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@tmatsuo
Copy link
Contributor

tmatsuo commented May 4, 2020

build

pip install failed for the following 5 directories:

  • appengine/flexible/memcache
  • dataflow/encryption-keys
  • dataflow/flex-templates/streaming_beam
  • ml_engine/online_prediction
  • pubsub/streaming-analytics

I'll first disable py-3.8 sessions for those directories.

I'll also file 5 bugs about those failures to discuss whether we should enable py-3.8 build again for each directory.

@tmatsuo tmatsuo added testing priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels May 4, 2020
@tmatsuo tmatsuo self-assigned this May 4, 2020
tmatsuo pushed a commit to tmatsuo/python-docs-samples that referenced this issue May 4, 2020
tmatsuo pushed a commit that referenced this issue May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. testing type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant