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

parse_build_log: handle syntax errors in sync.profile

    XMLWordPrintable

Details

    • User Story
    • Resolution: Done
    • Not Evaluated
    • None
    • None
    • Test scripts
    • None
    • 2

    Description

      http://testresults.qt-project.org/ci/QtJsonDb_master_Integration/build_00739/linux-g%2B%2B_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64/log.txt.gz failed with:

      4/12/12 5:33:32 AM EST: String found where operator expected at /build/recipes/179081964/base/sync.profile line 36, near ""libedit""
4/12/12 5:33:32 AM EST: 	(Missing semicolon on previous line?)
4/12/12 5:33:32 AM EST: I couldn't parse /build/recipes/179081964/base/sync.profile, which I need to determine dependencies.
4/12/12 5:33:32 AM EST: The error was syntax error at /build/recipes/179081964/base/sync.profile line 36, near ""libedit""
4/12/12 5:33:32 AM EST:  at _qtqa_latest/scripts/qt/qtmod_test.pl line 444

      parse_build_log could not extract any of this. It should be able to.

      It would be rather dodgy to explicitly match that "I couldn't parse" line - this is a script we control, not some third-party thing, so we should be able to do something less fragile.
      For example, introducing a "standard error format" from our own scripts which parse_build_log will always know how to parse.

      Attachments

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

        Activity

          People

            rmcgover Rohan McGovern (Inactive)
            rmcgover Rohan McGovern (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes