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

Add an address sanitizer build to blocking CI for qtbase

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: P2: Important P2: Important
    • None
    • None
    • Test configurations
    • None
    • fe0e87c9a6 (qt/qtbase/dev) fe0e87c9a6 (qt/tqtc-qtbase/dev) 37fed2c22e (qt/qt5/dev) 37fed2c22e (qt/tqtc-qt5/dev) 76ca35c6e7 (qt/qt5/dev) 76ca35c6e7 (qt/tqtc-qt5/dev)

      We have been running nightly ASAN builds on our CodeChecker host, and recently (after QTBUG-101681 was fixed) the count of found issues for qtbase has been zero (not counting memory leaks).

      This ticket is about adding one ASAN enabled build to our blocking CI.

      Notes

      1. Even if no sanitizer issues are found, many tests FAIL! when built with address sanitizer. So the test run should differentiate itself from other builds and not care about the test results. In fact it should not even save XML test logs, because we don't want to store such testresults to skew the statistics.
        • One approach would be to removeĀ qt-testrunner from being TESTRUNNER and instead use a simple wrapper that greps for "ERROR: AddressSanitizer" and not found it ignores the test exit code.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

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

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes