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

CI log parsing should be smarter

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Not Evaluated
    • None
    • unversioned
    • Coin (obsolete)
    • None

    Description

      Take for example: https://codereview.qt-project.org/#/c/181773/
      Build log: http://testresults.qt.io/logs/qt/qtdeclarative/f9a1cc0b11533e22292d078072465d845ea3362a/OSXOSX_10_10x86_64OSXOSX_10_10x86_64Clangqtci-osx-10.10-x86_64-10f9f6Release_NoFramework/71cbe41f3c52c8b49f8acb39aa63c5f4d9b4d182/buildlog.txt.gz

      CI says: "Could not parse build log "

      But why? I'm pretty sure that CI used to be able to figure out compile errors from logs, e.g:

      items/qquickpathitemgenericrenderer.cpp:388:23: error: no matching function for call to 'qTriangulate'

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. COIN-16 parse_build_log.pl needs updates to capture more info

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              tosaraja Tony Sarajärvi
              w00t Robin Burchell
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes