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

Include the name of the FSM workload in the WorkloadFailure description

    • Fully Compatible
    • TIG D (12/11/15), TIG E (01/08/16)

      When a workload fails, the reported backtrace will refer to the location of where the function was defined. Suppose that workload B derives from workload A. If the failure happens in a function that isn't overridden by a workload B, then then backtrace will refer to the definition of the function in workload A. This leads to ambiguity in which workload caused a failure when multiple workloads sharing the same base workload were run concurrently or were composed with each other.

      [js_test:fsm_all] 2015-11-17T11:03:43.807-0500 ----
      [js_test:fsm_all] 2015-11-17T11:03:43.807-0500 Workload(s) completed in 626 ms: jstests/concurrency/fsm_workloads/indexed_insert_compound.js
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500 ----
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500 2015-11-17T11:03:43.807-0500 E QUERY    [thread1] Error: 20 threads threw
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500         Foreground
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500         Error: I was thrown in an indexed_insert_base.js function, but was actually running indexed_insert_compound.js
      [js_test:fsm_all] 2015-11-17T11:03:43.808-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         find@jstests/concurrency/fsm_workloads/indexed_insert_base.js:68:19
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         runFSM@jstests/concurrency/fsm_libs/fsm.js:43:13
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         ____MongoToSM_newFunction_temp/<@:10:9
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         main@jstests/concurrency/fsm_libs/worker_thread.js:104:17
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         ____MongoToSM_newFunction_temp@:7:1
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500         ____MongoToSM_newFunction_temp@:5:24
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.809-0500  :
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500 throwError@jstests/concurrency/fsm_libs/runner.js:329:23
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500 runWorkloads@jstests/concurrency/fsm_libs/runner.js:618:17
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500 serial@jstests/concurrency/fsm_libs/runner.js:631:13
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500 @jstests/concurrency/fsm_all.js:10:1
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500
      [js_test:fsm_all] 2015-11-17T11:03:43.810-0500 failed to load: jstests/concurrency/fsm_all.js
      

      Proposal is to include the workload name in the description of the WorkloadFailure.

            Assignee:
            jonathan.abrahams Jonathan Abrahams
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: