ScopedThreads used by parallel suite do not get TestData configuration

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: