Uploaded image for project: 'Qt Quality Assurance Infrastructure'
  1. Qt Quality Assurance Infrastructure
  2. QTQAINFRA-5755

Add an address sanitizer build to blocking CI for qtdeclarative

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • P2: Important
    • None
    • None
    • Test configurations
    • 64bb2e748 (dev)

    Description

      Since the last ASAN issue in qtdeclarative has been fixed ( QTBUG-105090 ) we should add a blocking test configuration in CI as soon as possible, in order to prevent regressions. It should be based on the existing qtbase ASAN configuration on OpenSUSE.

      qt5/coin/platform_configs/address_sanitizer_platforms.yaml

      Version: 2
Configurations: 
-
    Id: 'opensuse-15.4-host-asan'
    Template: 'qtci-linux-openSUSE-15.4-x86_64-50'
    Compiler: 'GCC'
    Features: ['Sccache', 'WarningsAreErrors', 'UseConfigure', 'UseAddressSanitizer']
    Configure arguments: '-nomake examples -developer-build'
    Environment variables: [
        'PATH={{.Env.CMAKE_MIN_SUPPORTED_BIN_PATH}}:{{.Env.PATH}}',
        'CMAKE_ARGS=-DOPENSSL_ROOT_DIR={{.Env.OPENSSL_HOME}}',
        'NON_QTBASE_CMAKE_ARGS=-DFFMPEG_DIR={{.Env.FFMPEG_DIR}}'
    ]

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. QTQAINFRA-5375 Enable ASAN build for Qt modules

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed
          relates to

          Suggestion - Public suggestions QTQAINFRA-4139 Run autotests under sanitizers (ASAN / UBSAN / TSAN)

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          resulted from

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-105090 tst_QQuickMenu AddressSanitizer: heap-use-after-free in QQmlData::signalHasEndpoint(int)

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              jimis Dimitrios Apostolou
              jimis Dimitrios Apostolou
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes