Inject iterations and threadCount into data object in fsm workloads

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.2.0-rc3
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • TIG C (11/20/15)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently threadCount and iterations aren't available as part of the "this" context for workloads. Thus, workloads that use these as parameters can only access what they're set to initially. When using the load multiplier, any workloads that use the initial versions of these parameters fail because the threadCount has changed from what they expect. If they could just look at data for the updated threadCount, they could pass again.

              Assignee:
              Judah Schvimer
              Reporter:
              Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: