When calling TSS, resmoke fails

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: evergreen.yml
    • None
    • DevProd Services & Integrations
    • Fully Compatible
    • ALL
    • Hide

      run 2 patches, in one of them, use the same changes made in the patch and in the other do not.
      evergreen patch -p mongodb-mongo-master -v enterprise-amazon-linux2023-arm64-all-feature-flags -t all -u -y -f

      as an example, look at how many tests were run in the task: queryableWT

      Show
      run 2 patches, in one of them, use the same changes made in the patch and in the other do not. evergreen patch -p mongodb-mongo-master -v enterprise-amazon-linux2023-arm64-all-feature-flags -t all -u -y -f as an example, look at how many tests were run in the task: queryableWT
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      See this patch that fixed those issues (But also has hard-coded the solution, so it's not an optimal solution)

      As part of this change:
      1. We need to change the default strategy to not include NotFlaky for now
      2. When I tried to override the strategy via some config, it did not work. I think it was trying to read an array, but the input is just a string (less urgent as long as we fix the default strategy)
      3. The fix @Sean Lyons helped me with (as seen in the linked patch below)
      4. For the sake of being able to roll the changes out gradually, enable turning on TSS per specific variants

      The patch: https://spruce.mongodb.com/task/mongodb_mongo_master_enterprise_amazon_linux2023_arm64_all_feature_flags_queryableWT_patch_ef80dbacc5bf03bc59d68c49387920d5eb94df60_693b07612918c20007a7febf_25_12_11_18_03_22/tests?execution=0&sorts=STATUS%3AASC

            Assignee:
            Ron Neuman
            Reporter:
            Ron Neuman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: