resmoke.py does not always respect --installDir

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Hide
      • Copy an old mongod binary (eg., 5.0) to ~/mongo.
      • Check out the latest master branch and do a debug build.
      • Run a js test that uses ShardingTest, eg:
        • python buildscripts/resmoke.py run --installDir=build/debug/install/bin  jstests/sharding/allow_partial_results.js
      • You'll get a failure due to mongod failing to start.  Resmoke provides new parameters such as backtraceLogFile that are not understood by the old mongod binary.
      Show
      Copy an old mongod binary (eg., 5.0) to ~/mongo. Check out the latest master branch and do a debug build. Run a js test that uses ShardingTest, eg: python buildscripts/resmoke.py run --installDir=build/debug/install/bin  jstests/sharding/allow_partial_results.js You'll get a failure due to mongod failing to start.  Resmoke provides new parameters such as backtraceLogFile that are not understood by the old mongod binary.
    • 156
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It seems that the js ShardingTest and ReplSetTest objects will always use binaries in ~/mongo/ if they are present, even when a different installation directory is specified in the resmoke --installDir parameter.

      In the best case, your js test will faily unexpectedly when setting up the cluster.  In the worst case you'll be silently testing a different binary than you expected.

            Assignee:
            Alex Neben
            Reporter:
            Steve Tarzia
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: