| commit | 1d1df74c480d525011f352f76010becb315eeca5 | [log] [tgz] |
|---|---|---|
| author | Clark Boylan <clark.boylan@gmail.com> | Fri Aug 22 14:41:55 2014 -0700 |
| committer | Clark Boylan <clark.boylan@gmail.com> | Fri Aug 22 14:41:55 2014 -0700 |
| tree | d6562a3767b5a63af223c8ef2e86dd11fa6f8595 | |
| parent | b93c2461d1f04d42a1e6e6bb4953ebaeb6f2287b [diff] |
Handle latest testtools tearDown checks Latest testtools checks that you only call tearDown once (it also checks that setUp is only called once). Zuul's test framework was calling tearDown from a cleanup which resulted in tearDown being called twice. Once by the test framework and once by zuul's testclasses cleanups. Just remove the explicit tearDown call in the cleanups and let the larger python tooling call tearDown for us. Change-Id: Id8eaa9da5153fdfe9b9f852d2c57838736cb7040