Prepend error messages to stack traces in concurrency suite

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.9
    • Affects Version/s: 3.1.8
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • TIG 9 (09/18/15)
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As a follow-up to SERVER-19808, there are a few other spots in the concurrency suite where error messages are not prepended to stack traces, which makes it harder to debug failures.

      Example output before the change:

      Workload teardown function threw an exception:
teardown@jstests/concurrency/fsm_workloads/rename_collection_chain.js:54:15
teardownWorkload@jstests/concurrency/fsm_libs/runner.js:322:9
runWorkloads/</<@jstests/concurrency/fsm_libs/runner.js:431:29
runWorkloads/<@jstests/concurrency/fsm_libs/runner.js:429:21
runWorkloads@jstests/concurrency/fsm_libs/runner.js:399:13
serial@jstests/concurrency/fsm_libs/runner.js:469:13
@jstests/concurrency/fsm_all.js:15:1

      After the change:

      Workload teardown function threw an exception:
testing errors

teardown@jstests/concurrency/fsm_workloads/rename_collection_chain.js:54:15
teardownWorkload@jstests/concurrency/fsm_libs/runner.js:319:9
runWorkloads/</<@jstests/concurrency/fsm_libs/runner.js:428:29
runWorkloads/<@jstests/concurrency/fsm_libs/runner.js:426:21
runWorkloads@jstests/concurrency/fsm_libs/runner.js:396:13
serial@jstests/concurrency/fsm_libs/runner.js:470:13
@jstests/concurrency/fsm_all.js:15:1

            Assignee:
            Kamran K. (Inactive)
            Reporter:
            Kamran K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: