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

Beta release is failed on Python 3.7 bot for Linux #3458

Closed
asvetlov opened this issue Dec 21, 2018 · 8 comments
Closed

Beta release is failed on Python 3.7 bot for Linux #3458

asvetlov opened this issue Dec 21, 2018 · 8 comments

Comments

@asvetlov
Copy link
Member

Travis job is here: https://travis-ci.com/aio-libs/aiohttp/jobs/166684135
Job restart doesn't help
@webknjaz do you have any idea?

@aio-libs-bot
Copy link

GitMate.io thinks the contributor most likely able to help you is @webknjaz.

Possibly related issues are #467 (Failed building wheel for aiohttp on Python 3.5.0rc1), #537 (Drop python 3.3 support), #2704 (Errors installing on 3.7 beta), #2674 (Auto patch ssl for Python 3.7-), and #1603 (1.3 Release).

@yjqiang
Copy link

yjqiang commented Dec 21, 2018

travis-ci/travis-ci#9815 (comment)
Looks like the same reason?

@asvetlov
Copy link
Member Author

But we have dist: xenial and sudo: required in travis config already: https://github.com/aio-libs/aiohttp/blob/master/.travis.yml#L6-L7

@webknjaz
Copy link
Member

Hi, I'll check this today in the evening 🌃. Flying ✈ currently.

@webknjaz
Copy link
Member

What @yjqiang is very close to our problem: Travis CI tries to grab Python 3.7 archive for Ubuntu 14.04 while it should be downloading one for Xenial. So something may be wrong with overriding global settings on the job level.
It doesn't seem to be related to @asvetlov's changes to .travis.yml either.

@webknjaz
Copy link
Member

Should be fixed by 4bad3dc. @yjqiang's guess was correct after all.

@asvetlov
Copy link
Member Author

Thanks, @webknjaz !

@lock
Copy link

lock bot commented Dec 22, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Dec 22, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Dec 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants