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

ScopedThreads used by parallel suite do not get TestData configuration

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.4
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • Hide
      ./mongo --nodb --eval 'TestData = new Object(); TestData.storageEngine = "wiredTiger"; load("jstests/libs/parallelTester.js"); print("TestData is " + tojson(TestData)); var t = new ScopedThread(function() { printjson(TestData || "TestData was not defined in ScopedThread"); }); t.start(); t.join()'
      
      MongoDB shell version: 3.1.4-pre-
      TestData is { "storageEngine" : "wiredTiger" }
      "TestData was not defined in ScopedThread"
      
      Show
      ./mongo --nodb --eval 'TestData = new Object (); TestData.storageEngine = "wiredTiger" ; load( "jstests/libs/parallelTester.js" ); print( "TestData is " + tojson(TestData)); var t = new ScopedThread(function() { printjson(TestData || "TestData was not defined in ScopedThread" ); }); t.start(); t.join()' MongoDB shell version: 3.1.4-pre- TestData is { "storageEngine" : "wiredTiger" } "TestData was not defined in ScopedThread"
    • Quint Iteration 4

      Proposal is to change the behavior only for ScopedThread instances that are started by the parallelTester, and not a general change to all ScopedThread instances. This means that the code given in "steps to reproduce" will continue to report a failure, but threads created in assert.parallelTests will now get the TestData configuration.

            Assignee:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: