/matplotlib

TST: Fixed `test_log_margins` test #7453

Merged
merged 1 commit into from Nov 13, 2016

Conversation

Reviewers

@dopplershift dopplershift

Assignees
No one assigned
Labels
Testing
Projects
None yet
Milestone
  v2.0.0
4 participants
@Kojoley @efiring @dopplershift @QuLogic
@Kojoley
Member

Kojoley commented Nov 13, 2016

Closes #7452
@Kojoley Kojoley TST: Fixed `test_log_margins` test

Some checks were not successful

2 failing and 1 successful checks
continuous-integration/appveyor/pr — AppVeyor build failed
Details
continuous-integration/travis-ci/pr — The Travis CI build failed
Details
coverage/coveralls — Coverage remained the same at 66.412%
Details
7f2a0ce

Kojoley added the Testing label Nov 13, 2016

Kojoley added this to the 2.0.1 (next bug fix release) milestone Nov 13, 2016

@dopplershift

dopplershift approved these changes Nov 13, 2016
View changes

👍

@efiring
Owner

efiring commented Nov 13, 2016

@Kojoley, peripheral note: the Travis failure was the pytest run, after 25 minutes; I've seen this failure more often than not. Is there anything that can be done about it?

@efiring efiring merged commit 8515322 into matplotlib:master Nov 13, 2016
1 of 3 checks passed

1 of 3 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
Details
continuous-integration/travis-ci/pr The Travis CI build failed
Details
coverage/coveralls Coverage remained the same at 66.412%
Details

@efiring efiring added a commit that referenced this pull request Nov 13, 2016

@efiring efiring Merge pull request #7453 from Kojoley/fix-test_log_margins 
TST: Fixed `test_log_margins` test
 e6f2222
@efiring
Owner

efiring commented Nov 13, 2016

back-ported to v2.x as e6f2222
@Kojoley
Member

Kojoley commented Nov 14, 2016 • edited

@efiring I've seen this failure on both nose and pytest previously. Today I have run test_mixedsubplots about 500 times plus the whole test_mplot3d.py about 1500 times and it did not fail a single time. Unfortunately I do not have any idea what it could be and how to reproduce this failure. We have to grab a diff image from travis/appveyor at least to understand what is going on there,

@QuLogic QuLogic modified the milestone: 2.0.1 (next bug fix release), 2.0 (style change major release) Dec 7, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment