-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Windows test fixes and CI with AppVeyor #1504
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
environment: | ||
matrix: | ||
- PYTHON: C:\\Python33 | ||
- PYTHON: C:\\Python34 | ||
- PYTHON: C:\\Python35 | ||
- PYTHON: C:\\Python33-x64 | ||
- PYTHON: C:\\Python34-x64 | ||
- PYTHON: C:\\Python35-x64 | ||
install: | ||
- "git submodule update --init typeshed" | ||
- "SET PATH=%PYTHON%;%PYTHON%\\Scripts;C:\\Python27;%PATH%" | ||
- "REN C:\\Python27\\python.exe python2.exe" | ||
- "python --version" | ||
- "python2 --version" | ||
build_script: | ||
- "pip install -r test-requirements.txt" | ||
- "python setup.py install" | ||
test_script: | ||
- cmd: python runtests.py -v |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule typeshed
updated
10 files
+27 −8 | stdlib/2.7/argparse.pyi | |
+1 −1 | stdlib/2.7/datetime.pyi | |
+7 −4 | stdlib/2.7/pprint.pyi | |
+3 −3 | stdlib/2.7/typing.pyi | |
+8 −5 | stdlib/2.7/urlparse.pyi | |
+1 −1 | stdlib/3/_ast.pyi | |
+1 −1 | stdlib/3/datetime.pyi | |
+3 −0 | stdlib/3/os/__init__.pyi | |
+3 −3 | stdlib/3/typing.pyi | |
+9 −8 | third_party/2.7/requests/api.pyi |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than having to remember to add 'pathfix' to tests that happen to have pathnames with slashes in the expected output, maybe you could always fix the path in the text up to the first colon, skipping this completely if the line starts with whitespace or there's whitespace in the stuff before that first colon (or there is no colon)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I considered this but was hesitant to add more magic to this code. If that's the preference, I certainly could, though. Do you suppose there are other [out] sections that might be affected by that change? Should that behavior be documented somewhere, maybe in comments in test/data.py?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only way to be sure is to survey all [out] sections of all test files. Or at least sample a bunch of different ones (some have a different format, the test prints the repr() of some Node).
I just worry that your current approach will mean that every time a new test requires [out pathfix] it will first be committed without the pathfix and then after some time someone will report that it's broken on Windows and someone has to remember how to fix it.