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

MONGO_CONFIG_OPTIMIZED_BUILD is not being set correctly.

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Build
    • ALL

      When I compile the profile_filter_bm benchmark locally, I get the following warning:

      {"t":{"$date":"2024-09-05T15:34:10.319Z"},"s":"I",  "c":"TEST",     "id":23049,   "ctx":"main","msg":"***WARNING*** MongoDB was built with --opt=off. Function timings may be affected. Always verify any code change against the production environment (e.g. --opt=on)."}
      

      However, I am compiling with --opt=on and I see -O2 being specified in the ninja file to build the benchmark. As far as I can tell, it is being compiled with optimizations, but the MONGO_CONFIG_OPTIMIZED_BUILD flag is not being set correctly.

      If I run other benchmarks, like service_entry_point_common_bm, I do not see this warning.

            Assignee:
            Unassigned Unassigned
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: