Remove unrelated tracebacks from test output
This mocks some calls the ThreadGroup when testing update and delete of the stack, resulting in tracebacks when the threads randomly run later on in the test suite. Change-Id: Ia1a376933c2e25b6cf0fe6a26f47e381cbb1a55e Fixes: bug #1182285
This commit is contained in:
parent
7b224c0fe0
commit
14354874de
|
@ -293,6 +293,8 @@ class stackServiceCreateUpdateDeleteTest(HeatTestCase):
|
|||
|
||||
parser.Stack.load(self.ctx, stack=s).AndReturn(stack)
|
||||
|
||||
self.man.tg = DummyThreadGroup()
|
||||
|
||||
self.m.ReplayAll()
|
||||
|
||||
self.assertEqual(self.man.delete_stack(self.ctx, stack.identifier()),
|
||||
|
@ -338,6 +340,9 @@ class stackServiceCreateUpdateDeleteTest(HeatTestCase):
|
|||
self.m.StubOutWithMock(stack, 'validate')
|
||||
stack.validate().AndReturn(None)
|
||||
|
||||
self.m.StubOutWithMock(threadgroup, 'ThreadGroup')
|
||||
threadgroup.ThreadGroup().AndReturn(DummyThreadGroup())
|
||||
|
||||
self.m.ReplayAll()
|
||||
|
||||
result = self.man.update_stack(self.ctx, old_stack.identifier(),
|
||||
|
|
Loading…
Reference in New Issue