-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:
-
Fully Compatible
-
ALL
-
v4.2, v4.0
-
-
STM 2019-07-29
-
18
-
1
We're attempting to use the same FlagBasedStepdownLifecycle instance across executions of the test suite. This would mean FlagBasedStepdownLifecycle.__should_stop == True the moment the second execution of the test suite begins. We should instead construct a new FlagBasedStepdownLifecycle instance when constructing a new _StepdownThread instance.
[executor] 2019-07-12T00:12:46.427-0400 Summary: All 5 test(s) passed in 10.96 seconds.
[ContinuousStepdown:job0] Starting the stepdown thread.
[ContinuousStepdown:job0] The stepdown thread is not running.
[executor:js_test:job0] 2019-07-12T00:12:46.429-0400 JSTest jstests/core/indexc.js marked as a failure by a hook's before_test.
Traceback (most recent call last):
File "/Users/maxh/debugging/mongo/buildscripts/resmokelib/testing/job.py", line 242, in _run_hooks_before_tests
self._run_hook(hook, hook.before_test, test)
File "/Users/maxh/debugging/mongo/buildscripts/resmokelib/testing/job.py", line 228, in _run_hook
hook_function(test, self.report)
File "/Users/maxh/debugging/mongo/buildscripts/resmokelib/testing/hooks/stepdown.py", line 97, in before_test
self._check_thread()
File "/Users/maxh/debugging/mongo/buildscripts/resmokelib/testing/hooks/stepdown.py", line 113, in _check_thread
raise errors.ServerFailure(msg)
buildscripts.resmokelib.errors.ServerFailure: The stepdown thread is not running.
- is caused by
-
-
- Closed
-