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

Integrations are failed with comment 'Could not parse build log :('

    XMLWordPrintable

Details

    • Bug
    • Resolution: Incomplete
    • P1: Critical
    • None
    • unversioned
    • Coin (obsolete)

    Description

      Builds are failed quite often with comment 'Could not parse build log '. The real root cause is different but it is hard to study because coin overwrite these failed logs after successfully build. But what I found the real issues in the logs are:

        • sh: /System/Library/Frameworks/Python.framework/Versions/2.7/bin/rm: No such file or directory
        • "C:/Program Files/Git/bin/sh.exe": g++: command not found

      I browsed through qt5.git integration in '5.8.0' and '5.8' branches during December and noticed ~50% of flakiness is due to this issue! So it is definitely worth of studying & fixing

      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
          relates to

          Bug - A problem which impairs or prevents the functions of the product. COIN-28 Frequent failures extracting test errors: Could not parse build log for execution phase testing errors

          • 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

          Bug - A problem which impairs or prevents the functions of the product. QTQAINFRA-1564 Could not parse build log for execution phase testing C:/Users/qt/work/qt/qt3d/tests/auto/render/filtercompatibletechniquejob

          • 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

              aakeskimo Aapo Keskimölö
              janihe Jani Heikkinen
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes