Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Fix double running of explicitly chosen tests. #7498
Conversation
QuLogic
added the
Testing
label
Nov 22, 2016
QuLogic
added this to the
2.1 (next point release)
milestone
Nov 22, 2016
|
BTW, I'm pretty sure intentionally specifying a test twice (on the command-line) used to work, so there is still a regression there. This PR only fixes the case where a test is listed once and incorrectly gets run twice. |
NelleV
changed the title from
[MRG] Fix double running of explicitly chosen tests. to [MRG+1] Fix double running of explicitly chosen tests.
Nov 22, 2016
|
Merging on the theory that the one appveyor test that failed is transient (the test already has a higher tolerance on windows than the other platforms). |
tacaswell
merged commit 1512bee
into matplotlib:master
Nov 23, 2016
QuLogic
deleted the
QuLogic:dedup-tests branch
Nov 23, 2016
QuLogic
changed the title from
[MRG+1] Fix double running of explicitly chosen tests. to Fix double running of explicitly chosen tests.
Nov 23, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
QuLogic commentedNov 22, 2016
Running
python tests.py matplotlib.tests....would run the chosen tests twice, causing errors when figures were closed from the first run and then missing in the second run. This is becausesys.argv + extra_argsproduces the test list twice.cc @Kojoley