Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-11114

Set optimization to --O0 for test_random_abort evergreen task

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.2.0, 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • 1
    • 2023-05-30 - 7.0 Readiness

      This ticket came out of WT-10789, the problem is that a variable was unfortunately optimized out. Evergreen defaults to running with -0g optimization level. From the manual page:

      -Og (Optimize debugging experience. -Og enables optimizations that do not interfere with debugging. It should be the optimization level of choice for the standard edit-compile-debug cycle, offering a reasonable level of optimization while maintaining fast compilation and a good debugging experience.)

      In a summary it is still possible that -Og can optimize out variables and is not guarrantee for developers to make sure that a particular variable will not be optimized. Setting the level to --O0 will fix this issue, which will be helpful in case WT-10789 repros again.

      Definition of Done
      The aim of this ticket is to change the evergreen task to use -O0 instead.

            jie.chen@mongodb.com Jie Chen
            jie.chen@mongodb.com Jie Chen
            0 Vote for this issue
            1 Start watching this issue