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

Warnings Plugin "Wind River Diab Compiler (C/C++)"-parser is missing support for fatal errors

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • warnings-plugin
    • Jenkins LTS 1.480.3
      Static Analysis Utilities 1.49
      Warnings Plug-in 4.23

    Description

      Given an existing job with a "Wind River Diab Compiler (C/C++)"-parser and the "Run always" option enabled,
      when the build produces a fatal warning,
      then I want it included in the results from the plugin.

      Below is an example of the output of a division by zero warning with the different supported severity levels.
      (based of Wind Rivier Diab Combiler User's Guide, B.3.6 "-e, Change diagnostic severity level")

      i, Information, equivalent to ignore.
         -ei1025
      
      w, Warning.
         -ew1025
      "main.c", line 5: warning (dcc:1025): division by zero
      
      e, Error (continue compilation).
         -ee1025
      "main.c", line 5: error (dcc:1025): division by zero
      
      f, Fatal error (terminate immediately).
         -ef1025
      "main.c", line 5: fatal error (dcc:1025): division by zero
      

      Also, if it can have a positive effect on the performance - some of the \s* in the parser's regex could be removed/changed to a fixed space based off the format examples above.

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          Interested in providing a pull request?

          drulli Ulli Hafner added a comment - Interested in providing a pull request?

          Code changed in jenkins
          User: Sebastian Seidl
          Path:
          .classpath
          src/main/java/hudson/plugins/warnings/parser/DiabCParser.java
          src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java
          src/test/resources/hudson/plugins/warnings/parser/diabc.txt
          http://jenkins-ci.org/commit/warnings-plugin/411af186120b2e4d5b04167121518e4c68ae5739
          Log:
          Fixed Issue JENKINS-17075:
          DiabCParser recognizes now a "fatal error".

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Sebastian Seidl Path: .classpath src/main/java/hudson/plugins/warnings/parser/DiabCParser.java src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java src/test/resources/hudson/plugins/warnings/parser/diabc.txt http://jenkins-ci.org/commit/warnings-plugin/411af186120b2e4d5b04167121518e4c68ae5739 Log: Fixed Issue JENKINS-17075 : DiabCParser recognizes now a "fatal error".

          Code changed in jenkins
          User: Sebastian Seidl
          Path:
          .classpath
          src/main/java/hudson/plugins/warnings/parser/DiabCParser.java
          src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java
          src/test/resources/hudson/plugins/warnings/parser/diabc.txt
          http://jenkins-ci.org/commit/warnings-plugin/6a9c77bbafa05ed3e921b2884e9e34bd7b86449c
          Log:
          Fixed Issue JENKINS-17075:
          DiabCParser recognizes now a "fatal error".

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Sebastian Seidl Path: .classpath src/main/java/hudson/plugins/warnings/parser/DiabCParser.java src/test/java/hudson/plugins/warnings/parser/DiabCParserTest.java src/test/resources/hudson/plugins/warnings/parser/diabc.txt http://jenkins-ci.org/commit/warnings-plugin/6a9c77bbafa05ed3e921b2884e9e34bd7b86449c Log: Fixed Issue JENKINS-17075 : DiabCParser recognizes now a "fatal error".

          Fix verified, thank you!

          stela Stefan Landström added a comment - Fix verified, thank you!

          People

            schlangguru Sebastian Seidl
            stela Stefan Landström
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: