[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-06-27 Thread STINNER Victor
STINNER Victor added the comment: Windows buildbots are green since at least 2 months, so I close this issue. There is one remaining issue, but specific to the Windows *installer*: see bpo-30716 and bpo-27425. -- dependencies: -Tests fail because of git's newline preferences on

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Steve Dower
Steve Dower added the comment: > Does Git support per-file settings like the svn:eol-style property in > Subversion or .hgeol in Mercurial? The .gitattributes file seems to be full of glob patterns, so I assume a full file path will work. However, that doesn't help with tarballs. Fixing the

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Does Git support per-file settings like the svn:eol-style property in Subversion or .hgeol in Mercurial? -- nosy: +serhiy.storchaka ___ Python tracker

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread R. David Murray
R. David Murray added the comment: Some of the tests (notably email tests) are *testing* platform line endings. In tests that I rewrote I did my best to make the tests independent of the line endings of checked in files (that is, constructing the files-to-test in the test itself instead of

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Steve Dower
Steve Dower added the comment: My vote would be to make the tests not presume anything about line endings, to the point of converting test files on the fly to be sure. I'm mostly free today (in a different city with nothing to do), so if my hotel internet will let me SSH to github then I can

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Zachary Ware
Zachary Ware added the comment: We really need to be able to function regardless of the core.autocrlf setting. See #27425 for more about the EOL issues. -- dependencies: +Tests fail because of git's newline preferences on Windows ___ Python tracker

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Zachary Ware
Changes by Zachary Ware : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware priority: normal -> critical versions: +Python 2.7, Python 3.5, Python 3.6 ___ Python tracker

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Jeremy Kloth
Jeremy Kloth added the comment: Tests are now failing due to end-of-line (?) differences. I did a quick reading of the devguide, but didn't see any mention of the settings to be used for Git on Windows wrt core.autocrlf. -- ___ Python tracker

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-11 Thread Jeremy Kloth
Jeremy Kloth added the comment: After ensuring that Git is available to the buildbot service, the initial update fails due to the existing build directory containing the Mercurial checkout. After manually removing the contents of the build directories, the update task successfully completes.

[issue29530] Windows buildbots broken by the migration to GitHub (meta issue)

2017-02-10 Thread STINNER Victor
New submission from STINNER Victor: (*) I noticed test_sax and test_random failures on Windows since CPython moved to GitHub. These failures seem to be caused by newlines: see issue #27425. (*) "AMD64 Windows7 SP1 3.x" fails on the "git" step with: 'git' is not recognized as an internal