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

Send binary version instead of evergreen version to symbolizer service

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.2, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v6.0
    • DAG 2022-05-30
    • 2

      Debug symbols mapper sends ${version_id} evergreen expansion to symbolizer service to associate build ID with an evergreen version in order to distinguish patch versions, but it does not help with the mainline versions on the waterfall page.

      In patches

      -patch-${version_id}

      is appended to mongodb build version:

      6.1.0-alpha-653-gb5c35e9-patch-628612eb2fbabe0be7217803
      

      But it's not the same with the mainline versions. Nothing is appended to it there:

      6.1.0-alpha-558-gd3d37be
      

      On the mainline the values of ${version_id} looks like this:

      mongodb_mongo_master_1391cc6cdd8968ee8ce4336a0d566e76906efcc5
      

      This values are not printed in backtraces, so it can't be used during the search of debug symbols.

      To fix that mongodb build version could be sent instead:

      $ mongod --version
      
      db version v6.1.0-alpha-558-gd3d37be
      Build Info: {
          "version": "6.1.0-alpha-558-gd3d37be",
          "gitVersion": "d3d37be21fdac8e773c30db8ba542bbf7d9f5f4f",
          "modules": [
              "enterprise"
          ],
          "allocator": "system",
          "environment": {
              "distarch": "x86_64",
              "target_arch": "x86_64"
          }
      }
      

      This value is printed in backtraces:

      • example from waterfall
        ... "processInfo":{"mongodbVersion":"6.1.0-alpha-675-g1391cc6" ...
        
      • example from patch
        ... "processInfo":{"mongodbVersion":"6.1.0-alpha-653-gb5c35e9-patch-628612eb2fbabe0be7217803" ...
        

      This way mainline versions and patch versions can be distinguished correctly.

            Assignee:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Reporter:
            mikhail.shchatko@mongodb.com Mikhail Shchatko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: