Fix errors in integrity tests
See original GitHub issueFirst of all, I’m not sure this is even caused by this project, but after fixing #1010 it seemed from the error logs that CI should start working again. However, judging from #1007 and #1008 there is an issue with Python 3.3 on the 1.x
branch and Python 3.8-dev on master
.
The problem with Python 3.8-dev on master
may be a non-issue since the URL that seems to cause it definitely works now, so could someone please re-run the CI for #1007?
For Python 3.3 on the 1.x
branch, it seems to be caused by Python 3.3 end of life that in turn causes the binary package to be removed, and the fix seems to be just
I was considering making this two issues, but since the effort for fixing them seems very small, I could not bring myself to justify it. Right now this issue is mostly for ensuring that this get fixed, and that it is fixed the right way.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Update
I have verified that the failing for #1007 is periodical, so I will close and reopen the PR to re-run it, since I found out that it is possible to re-run this way. We still need to fix 1.x however.
Proposals for solution:
bionic
(Newest LTS so there might be a Python 3.3 package for it in place of the missing one forxenial
)Any thoughts?
Closing because we have since moved CI to Github actions.