Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48051

IAR Compiler (C/C++) parsing takes very long time

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • warnings-plugin
    • None
    • Jenkins 2.73.3
      Warnings Plugin 4.63
    • 5.0.0-beta3

      Our job is parsing both GNU C Compiler 4 (gcc) and IAR Compiler (C/C++) warnings. GNU parsing takes only few seconds but IAR parsing is very slow (about 25min). Console log looks like following:

      09:46:43 [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)

      09:46:48 Skipping warnings blame since Git is the only supported SCM up to now.

      09:46:48 [WARNINGS] Parsing warnings in console log with parser IAR Compiler (C/C++)

      10:11:41 Skipping warnings blame since Git is the only supported SCM up to now.

      10:11:41 [WARNINGS] Ignore new warnings since this is the first valid build

      10:11:41 [WARNINGS] Plug-in Result: Success - no threshold has been exceeded

      With warnings plugin version 4.57 IAR parsing takes less than second. Not sure if it can be that fast either. Console log is:
      13:47:49 [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)

      13:47:55 [WARNINGS] Parsing warnings in console log with parser IAR Compiler (C/C++)

      13:47:55 [WARNINGS] Computing warning deltas based on reference build #8

      13:47:55 [WARNINGS] Ignore new warnings since this is the first valid build

      13:47:55 [WARNINGS] Plug-in Result: Success - no threshold has been exceeded

      Only change between those builds is warnings plugin version. I see there has been made improvements to IAR parser in version 4.63 but I guess parsing shouldn't take that much time. Console log size is 29MB.

      There are no warnings found in any build so can't be sure how different versions of plugin works.

          [JENKINS-48051] IAR Compiler (C/C++) parsing takes very long time

          Ulli Hafner added a comment -

          Interested in looking into the parser sources on your own? I have no idea why the changes increase the parsing time in such a way? Maybe we should revert that commit.

          Ulli Hafner added a comment - Interested in looking into the parser sources on your own? I have no idea why the changes increase the parsing time in such a way? Maybe we should revert that commit.

          I took a look to the change but can't say quickly what could cause this problem.

          But I would recommend to revert that commit as it is causing also JENKINS-46131. I have seen that error too on our builds.

          Jaakko Finning added a comment - I took a look to the change but can't say quickly what could cause this problem. But I would recommend to revert that commit as it is causing also  JENKINS-46131 . I have seen that error too on our builds.

            drulli Ulli Hafner
            jfinning Jaakko Finning
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: