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

Travis-ci: AMD64 build is failing #16

Open
sanjaymsh opened this issue Oct 20, 2020 · 3 comments
Open

Travis-ci: AMD64 build is failing #16

sanjaymsh opened this issue Oct 20, 2020 · 3 comments

Comments

@sanjaymsh
Copy link

Hi,

The travis-ci build is failing with below error:
"Downloading archive: https://storage.googleapis.com/travis-ci-language-archives/python/binaries/ubuntu/16.04/x86_64/python-3.3.tar.bz2
0.11s$ curl -sSf --retry 5 -o python-3.3.tar.bz2 ${archive_url}
curl: (22) The requested URL returned error: 404 Not Found
Unable to download 3.3 archive. The archive may not exist. Please consider a different version.

"

Seems that the python:3.3 support is not available for amd64 on travis.

Please look into this.

Thanks !!

@Carreau
Copy link
Member

Carreau commented Oct 21, 2020

Where do you see this ? Python 3.3 is end of life anyway and this package will not get any update so I'm not sure why/what you want us to do.

@sanjaymsh
Copy link
Author

sanjaymsh commented Oct 21, 2020

Hi @Carreau , so python:3.3 should be removed from .travis.yml. isn't it?
It is still in .travis.yml file. And this is the reason of build fail.

language: python
python:
- "nightly"
- 3.4
- 3.3
- 2.7
sudo: false

Thanks !!

@Carreau
Copy link
Member

Carreau commented Oct 23, 2020

And this is the reason of build fail.

Build fail where ? The test for this repository works. Last CI run from 2018 is green, and last meaning full commit from 2017 also. And there is no pull requests.

so python:3.3 should be removed from .travis.yml.

Well that's like saying the titanic need to get cleaned before arriving in new york, sure you could make it float again but why ? This repository will likely never get any new commits, and if we update it we are likely to remove python 3.3, 3.4, 3.5, and 3.6. But there is no reasons to.

So I'm not sure I understand:

  • where is it failing ?
  • Why does that matter ?
  • What are you trying to achieve ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants