[3.4] Backport CI config from master#2475
Conversation
|
Ok, here is my first attempt for enable Travis CI and AppVeyor to the 3.4 branch. It should help to test automatically backported security fixes. I'm not sure about enabling CodeCov. Do we need CodeCov on 3.4? Once this PR will work and be merged, I will backport it to the 3.3 branch. |
Sorry, something went wrong.
|
The doc job failed with: => need to backport the commit e7ffb99. |
Sorry, something went wrong.
|
The Travis CI job failed on: Need to remove this from .travis.yml. At least, the compilation succeeded ;-) AppVeyor failed on: Need to replace the option with --slow. |
Sorry, something went wrong.
|
I removed CodeCov config from .github/ and tried to fix CI failures. |
Sorry, something went wrong.
|
New failure of the Travis CI doc job: |
Sorry, something went wrong.
|
Failure of the Travis CI python job: |
Sorry, something went wrong.
zware
left a comment
There was a problem hiding this comment.
Looks mostly fine, a couple of things pointed out below.
Sorry, something went wrong.
|
I removed the Travis CI doc job. It requires too many changes to fix it. The doc wasn't tested, so it's not like it's a regresion. Moreover, security fixes don't touch Doc/ usually, so it should be fine. |
Sorry, something went wrong.
In that case, let's remove the changes in |
Sorry, something went wrong.
|
4 tests failed on Windows: |
Sorry, something went wrong.
|
On Travis CI, the same 2 test_imaplib tests failed. |
Sorry, something went wrong.
|
@zware: "In that case, let's remove the changes in Doc/ as well." Oh, it's a mistake. I reverted most Doc changes, but I forgot one. It's now fixed. I backported another fix for test_imaplib which removes the 2 failing tests. |
Sorry, something went wrong.
|
Oh yeah! Travis CI now pass. AppVeyor will likely fail in test_os again, I didn't identifier the right commit to cherry-pick yet. @serhiy-storchaka: Do you recall which commit fixed test_os random failures on os.walk on Windows? see #2475 (comment) failures |
Sorry, something went wrong.
brettcannon
left a comment
There was a problem hiding this comment.
This review is only for the Travis file.
Sorry, something went wrong.
|
Ok, the Python test suite now pass on Linux (Travis CI) and Windows (AppVeyor). Summary of the PR:
This PR doesn't contain:
@brettcannon: I really prefer to fix all CI issues in a single PR, and not have to handle 2 or 3 PR to get a working CI. @zware: Would you mind to review this PR? You worked on these CI recently, so you should be able to check it :-) @larryhastings: Would you mind to review this PR? It should help to be more confident when merging security fixes in 3.4, since the 3.4 buildbots were removed. Thanks @serhiy-storchaka, I backported you bpo-23808 fix and it seems like it was just enough ;-) |
Sorry, something went wrong.
zware
left a comment
There was a problem hiding this comment.
LGTM, though I have added a suggestion.
Sorry, something went wrong.
|
@Haypo I have no problem with rolling up the fixes to go with the |
Sorry, something went wrong.
|
FWIW, there's some automation when cutting releases that removes dotfiles we don't want to leak into Python release tarballs. New dotfiles like .travis.yaml (and ".mention-bot", and ".github") need to be explicitly pruned. I'm gonna follow up and make sure this happens for 3.6.2 final and 3.6.4rc1. In the future, we release managers would appreciate a heads-up warning us when people add new dotfiles to the root of cpython, so we can make sure we don't ship them. |
Sorry, something went wrong.
I guess that you use some scripts, are they public? |
Sorry, something went wrong.
|
@Haypo my guess is https://github.com/python/release-tools, but there's no explicit dot file list that I see there so I may be wrong |
Sorry, something went wrong.
|
Brett's link to release-tools is the right place. The logic to strip the dotfiles is hidden inside. But please don't touch it right now. @ned-deily has done a lot of work on it to update it to Github, but he hasn't checked in those changes yet. I appreciate you being willing to fix release-tools when you add new dotfiles but please wait until release.py doesn't call "hg" anymore ;-) |
Sorry, something went wrong.
|
@larryhastings: Please see my summary of this PR, #2475 (comment) Technically, I don't think that you can merge a PR if the CI fails. So it's not posisble to add the CI config in one PR and then fix failing tests. I could do the opposite, but it's not possible to make a PR depends on another one. Moreover, I used this issue to see which tests on the CI and test my fixes. |
Sorry, something went wrong.
|
I just rebased this PR on top of the 3.4 branch, since many security PRs just have been merged. So it would help to check if everything is fine on 3.4 :-) |
Sorry, something went wrong.
Oh, everything is not fine, test_subprocess fails: http://bugs.python.org/issue30730#msg298218 |
Sorry, something went wrong.
|
Oh, I forgot that null character/byte errors were of type TypeError before 3.5. The simplest fix is changing corresponding |
Sorry, something went wrong.
* Add .travis.yml for Travis CI * Add .github/ for AppVeyor and CodeCov.
The regen-all Makefile rule doesn't exist in Python 3.4, only since Python 3.5 and newer (and 2.7).
tzdata resource doesn't exist in Python 3.4.
Fix test_invalid_cmd() and test_invalid_env(), TypeError is raised on Python 3.4. (cherry picked from commit 5e22721)
It took me one minute to understand that this commit comes from PR #2363 which is not merged yet :-) I changed the commit message and added it at the end of this PR. I also rebased this PR on top of 3.4. |
Sorry, something went wrong.
|
Yeah, tests pass again \o/ @larryhastings: Ok, it's your turn ;-) |
Sorry, something went wrong.
|
(The PR was already approved by 3 core devs, maybe 4 if you include myself.) |
Sorry, something went wrong.
|
I look forward to 3.4 entering the age of automation! |
Sorry, something went wrong.
Copy link Copy MarkdownSorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.