Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18739

Replication unit tests fail when run in parallel

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.0.13, 3.1.4
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • Hide

      python buildscripts/resmoke.py --suites=unittests -j24

      Show
      python buildscripts/resmoke.py --suites=unittests -j24
    • 0

      When running the unit tests with a high degree of parallelism, I consistently see failures in these unit tests:

      2015-05-29 11:01:36,561 [executor:cpp_unit_test] Summary: 154 test(s) ran in 19.33 seconds (151 succeeded, 56 were skipped, 3 failed, 0 errored)
          The following tests failed (with exit code):
              build/cached/mongo/db/repl/repl_coordinator_impl_elect_v1_test (17)
              build/cached/mongo/db/repl/repl_coordinator_impl_test (17)
              build/cached/mongo/db/repl/repl_coordinator_impl_elect_test (17)
      2015-05-29 11:01:36,561 [resmoke] ================================================================================
      2015-05-29 11:01:36,561 [resmoke] Summary of unittests suite: 154 test(s) ran in 19.33 seconds (151 succeeded, 56 were skipped, 3 failed, 0 errored)
          cpp_unit_tests: 154 test(s) ran in 19.33 seconds (151 succeeded, 56 were skipped, 3 failed, 0 errored)
              The following tests failed (with exit code):
                  build/cached/mongo/db/repl/repl_coordinator_impl_elect_v1_test (17)
                  build/cached/mongo/db/repl/repl_coordinator_impl_test (17)
                  build/cached/mongo/db/repl/repl_coordinator_impl_elect_test (17)
      
      

        1. out.txt
          1.55 MB
          Adam Midvidy

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            adam.midvidy Adam Midvidy
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: