Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Backport 7338, TST: Use pytz CI #7343

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

Merged
merged 1 commit into from
Feb 26, 2016

Conversation

jakirkham
Copy link
Contributor

Related: #7336
Related: #7337
Related: #7338

This should allow for some tests that require pytz to run during CI.

@charris charris added this to the 1.11.0 release milestone Feb 25, 2016
This should allow for some tests that require `pytz` to run during CI.
@jakirkham jakirkham force-pushed the use_pytz_ci_backport branch from c5f3c47 to ee53e0f Compare February 25, 2016 18:32
@jakirkham
Copy link
Contributor Author

Note that given the recent adjustment to test_datetime we see 6 known failures and 13 skips on Python 2.6. With this change, we now see 7 known failures and 11 skips on Python 2.6. This shows that the two pytz tests are run and that one is marked as a known failure on Python 2.6. All other Pythons see no change in the known failure only in the skips. So, this is working as intended.

charris added a commit that referenced this pull request Feb 26, 2016
@charris charris merged commit d5c3832 into numpy:maintenance/1.11.x Feb 26, 2016
@charris
Copy link
Member

charris commented Feb 26, 2016

Thank @jakirkham .

@jakirkham jakirkham deleted the use_pytz_ci_backport branch February 26, 2016 00:42
@jakirkham
Copy link
Contributor Author

Of course.

@charris charris changed the title TST: Backport 1.11.x - Use pytz CI Backport 7338, TST: Use pytz CI Mar 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants